SignalWiki - User contributions [en-gb]

User:Charlie

2018-12-17T01:31:55Z

Charlie: Undo revision 10739 by Charlie (talk)

What, were you expecting to see something here?

User:Charlie

2018-12-17T01:31:30Z

Charlie: PHP 7.2 test.

What, were you expecting to see something here?

<Testing PHP 7.2>

File:Ksec icon 128.jpg

2018-02-01T03:07:39Z

Charlie:

File:Kbr icon.png

2018-02-01T03:04:23Z

Charlie:

File:Fmbg 128.png

2018-02-01T03:01:25Z

Charlie:

File:Fkih 128.png

2018-02-01T03:01:08Z

Charlie:

File:Rk 128.png

2018-02-01T02:57:23Z

Charlie:

File:Eg 128.png

2018-02-01T02:56:09Z

Charlie:

File:Nwh 128.png

2018-02-01T02:51:46Z

Charlie:

File:Khez 128.png

2018-02-01T02:49:34Z

Charlie:

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:29:08Z

Charlie: /* Overview of the handling of PbZ-D trains */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''0 Cargo'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''Cargo+'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the siding tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Some electric trains also drive to the tank plate for cleaning, also.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the cars of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, the order of the trains and the time interval can strongly vary; different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight cars from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is a Thursday except in the summer of 2016 when it's Tuesday, and in the autumn of 2016 on both Tuesday and Thursday.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, cars are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with widely varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''SFS GWB!! ^xxx/yyy/zzz“'' have to be sent onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locos that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already-stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the movement orders window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option RTZ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]])
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''Cargo +''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant (Regel).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loco uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loco couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loco uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loco couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continues its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:26:21Z

Charlie: /* Freight trains and staff changes */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''0 Cargo'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''Cargo+'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the siding tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Some electric trains also drive to the tank plate for cleaning, also.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the cars of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, the order of the trains and the time interval can strongly vary; different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight cars from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is a Thursday except in the summer of 2016 when it's Tuesday, and in the autumn of 2016 on both Tuesday and Thursday.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, cars are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with widely varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''SFS GWB!! ^xxx/yyy/zzz“'' have to be sent onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locos that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already-stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the movement orders window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option RTZ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]])
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''Cargo +''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:25:42Z

Charlie: /* Additional traffic (Zusatzverkehr) */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the siding tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Some electric trains also drive to the tank plate for cleaning, also.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the cars of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, the order of the trains and the time interval can strongly vary; different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight cars from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is a Thursday except in the summer of 2016 when it's Tuesday, and in the autumn of 2016 on both Tuesday and Thursday.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, cars are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with widely varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''SFS GWB!! ^xxx/yyy/zzz“'' have to be sent onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locos that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already-stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the movement orders window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option RTZ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]])
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''Cargo +''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:24:28Z

Charlie: /* Rescue train */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the siding tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Some electric trains also drive to the tank plate for cleaning, also.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the cars of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, the order of the trains and the time interval can strongly vary; different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight cars from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is a Thursday except in the summer of 2016 when it's Tuesday, and in the autumn of 2016 on both Tuesday and Thursday.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, cars are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with widely varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''SFS GWB!! ^xxx/yyy/zzz“'' have to be sent onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locos that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already-stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the movement orders window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option RTZ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:22:51Z

Charlie: /* Stabled trains at program start */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the siding tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Some electric trains also drive to the tank plate for cleaning, also.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the cars of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, the order of the trains and the time interval can strongly vary; different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight cars from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is a Thursday except in the summer of 2016 when it's Tuesday, and in the autumn of 2016 on both Tuesday and Thursday.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, cars are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with widely varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''SFS GWB!! ^xxx/yyy/zzz“'' have to be sent onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locos that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already-stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:21:38Z

Charlie: /* Movement orders */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the siding tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Some electric trains also drive to the tank plate for cleaning, also.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the cars of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, the order of the trains and the time interval can strongly vary; different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight cars from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is a Thursday except in the summer of 2016 when it's Tuesday, and in the autumn of 2016 on both Tuesday and Thursday.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, cars are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with widely varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''SFS GWB!! ^xxx/yyy/zzz“'' have to be sent onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locos that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:20:23Z

Charlie: /* Additional remarks in the train overview window */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the siding tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Some electric trains also drive to the tank plate for cleaning, also.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the cars of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, the order of the trains and the time interval can strongly vary; different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight cars from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is a Thursday except in the summer of 2016 when it's Tuesday, and in the autumn of 2016 on both Tuesday and Thursday.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, cars are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with widely varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''SFS GWB!! ^xxx/yyy/zzz“'' have to be sent onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locos that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:20:09Z

Charlie: /* Additional remarks in the train overview window */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the siding tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Some electric trains also drive to the tank plate for cleaning, also.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the cars of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, the order of the trains and the time interval can strongly vary; different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight cars from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is a Thursday except in the summer of 2016 when it's Tuesday, and in the autumn of 2016 on both Tuesday and Thursday.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, cars are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with widely varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be sent onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locos that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:16:28Z

Charlie: /* PbZ-D trains */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the siding tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Some electric trains also drive to the tank plate for cleaning, also.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the cars of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, the order of the trains and the time interval can strongly vary; different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight cars from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is a Thursday except in the summer of 2016 when it's Tuesday, and in the autumn of 2016 on both Tuesday and Thursday.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, cars are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with widely varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:13:35Z

Charlie: /* Switchers */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the siding tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Some electric trains also drive to the tank plate for cleaning, also.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the cars of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, the order of the trains and the time interval can strongly vary; different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight cars from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:10:43Z

Charlie: /* Stabling of DB Regio-trains */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the siding tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Some electric trains also drive to the tank plate for cleaning, also.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the wagons of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, ans so the order of the trains and the time interval can strongly vary, different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight wagons from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:07:53Z

Charlie: /* Stabling of locomotives */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the sidings tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Because of the latter, some electric trains also drive to the tank plate.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the wagons of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, ans so the order of the trains and the time interval can strongly vary, different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight wagons from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:07:26Z

Charlie: /* Stabling of locomotives */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locos of DB-Region are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locos of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the sidings tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Because of the latter, some electric trains also drive to the tank plate.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the wagons of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, ans so the order of the trains and the time interval can strongly vary, different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight wagons from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:06:03Z

Charlie: /* PbZ-D trains */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locs of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locs of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the sidings tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Because of the latter, some electric trains also drive to the tank plate.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the wagons of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, ans so the order of the trains and the time interval can strongly vary, different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight wagons from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the [[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]].

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:04:48Z

Charlie: /* PbZ-D trains */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locs of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locs of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the sidings tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Because of the latter, some electric trains also drive to the tank plate.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the wagons of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, ans so the order of the trains and the time interval can strongly vary, different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight wagons from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the ''[Dispatching in Zentralstellwerk Würzburg Hbf#Overview_of_the_handling_of_PbZ-D_trains|Overview of PbZ-D trains]]''.

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T03:02:11Z

Charlie: /* Stabling of extra trains */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see [[Dispatching in Zentralstellwerk Würzburg Hbf#List_of_extra_trains|List of extra trains]]) terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locs of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locs of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the sidings tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Because of the latter, some electric trains also drive to the tank plate.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the wagons of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, ans so the order of the trains and the time interval can strongly vary, different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight wagons from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the ''„[[Dispatching in Zentralstellwerk Würzburg Hbf#Overview of PbZ-D trains|Overview of PbZ-D trains]]“.

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T02:56:52Z

Charlie: /* Generic Panel NVE/NWR (ESTW) */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur with freight trains in NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see "Overview of extra trains") terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locs of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locs of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the sidings tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Because of the latter, some electric trains also drive to the tank plate.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the wagons of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, ans so the order of the trains and the time interval can strongly vary, different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight wagons from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the ''„[[Dispatching in Zentralstellwerk Würzburg Hbf#Overview of PbZ-D trains|Overview of PbZ-D trains]]“.

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T02:56:21Z

Charlie: /* Generic Panel NVE/NWR (ESTW) */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighbouring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Würzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher at NWH must set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable, tracks 501-503 are used for the direction north-south, and tracks 504-506 are for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via tracks 501 and 506. A stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. Tracks 604 and 605 are used for pass-through train traffic; track 606 is for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. The route must be set manually in ESTW for this to happen.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, to ensure that during the staff change no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur in freight trains by NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling within the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see "Overview of extra trains") terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locs of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locs of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the sidings tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Because of the latter, some electric trains also drive to the tank plate.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the wagons of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, ans so the order of the trains and the time interval can strongly vary, different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight wagons from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the ''„[[Dispatching in Zentralstellwerk Würzburg Hbf#Overview of PbZ-D trains|Overview of PbZ-D trains]]“.

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T02:50:02Z

Charlie: /* Freight trains and staff changes */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver being relieved of duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locos as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighboring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Wurzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running here in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher NWH has to set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable the tracks 501-503 are used for the direction north-south, and the tracks 504-506 for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via the tracks 501 and 506, a stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. The tracks 604 and 605 are used for pass-through train traffic, track 606 for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. For this the route in the ESTW must then be manually set.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, so that ensure that during the LPW no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur in goods trains by NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling at the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see "Overview of extra trains") terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locs of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locs of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the sidings tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Because of the latter, some electric trains also drive to the tank plate.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the wagons of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, ans so the order of the trains and the time interval can strongly vary, different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight wagons from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the ''„[[Dispatching in Zentralstellwerk Würzburg Hbf#Overview of PbZ-D trains|Overview of PbZ-D trains]]“.

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T02:47:35Z

Charlie: /* Information about the timetable */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The vehicle composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets ''no'' steering number or a ''wrong'' steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver going off duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locs as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighboring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Wurzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running here in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher NWH has to set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable the tracks 501-503 are used for the direction north-south, and the tracks 504-506 for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via the tracks 501 and 506, a stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. The tracks 604 and 605 are used for pass-through train traffic, track 606 for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. For this the route in the ESTW must then be manually set.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, so that ensure that during the LPW no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur in goods trains by NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling at the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see "Overview of extra trains") terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locs of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locs of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the sidings tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Because of the latter, some electric trains also drive to the tank plate.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the wagons of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, ans so the order of the trains and the time interval can strongly vary, different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight wagons from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the ''„[[Dispatching in Zentralstellwerk Würzburg Hbf#Overview of PbZ-D trains|Overview of PbZ-D trains]]“.

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T02:44:32Z

Charlie: /* Information about the timetable */

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the Nuremberg-Leipzig line from 03-01-2016 until 05-09-2016
*Engineering works on the SFS (HSL) Göttingen-Hannover line from 14-07-2016 until 03-09-2016

The regional trains' timetable is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations, or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 to 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such is implemented for the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The train composition of freight trains is typical.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets no or a wrong steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver going off duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locs as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighboring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Wurzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running here in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher NWH has to set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable the tracks 501-503 are used for the direction north-south, and the tracks 504-506 for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via the tracks 501 and 506, a stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. The tracks 604 and 605 are used for pass-through train traffic, track 606 for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. For this the route in the ESTW must then be manually set.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, so that ensure that during the LPW no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur in goods trains by NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling at the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see "Overview of extra trains") terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locs of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locs of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the sidings tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Because of the latter, some electric trains also drive to the tank plate.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the wagons of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, ans so the order of the trains and the time interval can strongly vary, different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight wagons from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the ''„[[Dispatching in Zentralstellwerk Würzburg Hbf#Overview of PbZ-D trains|Overview of PbZ-D trains]]“.

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Dispatching in Zentralstellwerk Würzburg Hbf

2017-11-29T02:38:54Z

Charlie: Reverted edits by SignalAdmin (talk) to last revision by ErwinL

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf|EN=Dispatching in Zentralstellwerk Würzburg Hbf|NL=Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf}}
{{EnglishConstruction}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is a brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/wuerzburg Sp Dr S 600-Zentralstellwerk Würzburg Hbf panel] here.

== Zentralstellwerk Würzburg Hbf ==

===Lines===


===Neighbouring Dispatching Areas===
Let's have a look at our neighbouring dispatchers:


===Stations and Sidings===


===Overview Offering Trains Using DET===

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsNWH|EN}}

=== Abbreviations ===

[[File:line_Würzburg.png|760px|thumb|none|Würzburg : destinations as used in timetable]]

{{ShortNames:TableDetailsNWH|EN}}

=== Track Lengths / Speed limits ===
{{TrackLengths:TableDetailsNWH|EN|Würzburg Hbf}}

=== Auto fleeting ===
{{Autofleet:TableDetailsNWH|DE}}

==Information about the timetable==

The simulation is based on the timetable of the year 2016. For the long-distance trains, planned changes, as a result of engineering works on different lines, have been incorporated into the timetable. Influences on the timetable were:
*Signal box failure in Mülheim (Ruhr)-Styrum until 20-03-2016
*Engineering works on the line Nuremberg-Leipzig from 03-01-2016 until 05-09-2016
*Engineering workson the SFS (HSL) Göttingen-Hannover from 14-07-2016 until 03-09-2016

The timetable of the regional trains is based on the first half of 2016. Therefore, changes in the course of the second half of 2016 (replacement of single-deck trains by double-deck trains on the Frankfurt-Würzburg route, and the extension of the corresponding Regional Express service to Bamberg) are not included in the timetable. Deviations during the school holidays are not included either. The same applies to deviating times, final destinations or train compositions which only occurred one or just a few days in the year.

Some freight trains are also limited to special periods. This applies in particular to the diverted freight trains from Leipzig via Fulda to Würzburg and back in the period 01-10-2016 till 05-09-2016. For the freight trains' timetable the period from January to March 2016 is taken as the basis, and as such implementedfor the rest of the year. Limited time periods in 2016 were also taken into account. For some freight trains, the train number was changed in 2016. Only one train number for the entire year has been used for these cases. For a number of trains the route and travel times had to be partly estimated. The train composition of freight trains is only indicative.

===High-speed line (SFS) and steering numbers ===

On the high-speed line (SFS), traffic is running to the north and from Lohr using steering numbers. The steering numbers are assigned as follows:
*Steering number 1 - direction Lohr (NLO)
*Steering number 2 - direction Burgsinn (NBN)
*Steering number 5 - from Lohr

Trains from Lohr already have the steering number 5 assigned. For the trains to the north the steering number is automatically assigned when the train is on the SFS. After passing Rohrbach, all steering numbers are automatically deleted.

This process works for all trains being scheduled via the SFS. If the dispatcher routes other trains via the SFS, it may be that the train in question gets no or a wrong steering number assigned. In that case, the dispatcher must either change the steering number himself or manually set the routes in Rohrbach.

===Northern track to/from Rottendorf (NRTD) ===

Between Rottendorf (NRTD) and Würzburg Hbf (NWH), a third track runs north of the main line. This northern track is normally used in GWB (bi-directional operation) for trains from/to Schweinfurt. Some trains to Kitzingen/Nuremberg also run via this track. Which trains the dispatcher should send via the northern track to Rottendorf as per timetable, is indicated in the remarks for these trains.

However, in principle all available tracks can be chosen according to the dispatcher's preferences, as in Rottendorf all destinations can be reached from any track.

=== Freight trains and staff changes===

Freight trains run in all directions and in all possible ways. For some freight trains to the west, the Remarks indicate how they should routed according to the timetable. Where the remark has the following meaning:
*SFS - High speed line
*NWR - Würzburg Rbf
*Fbn - over the Fernbahn to Würzburg Rbf Zell (NWR U)

Fbn is also indicated for trains from the opposite direction, if these run from NWR U via the Fernbahn tracks to NWH. All other freight trains from/to NWR run via the freight tracks. Trains which are marked with (> NWR) must be routed via the Rbf, since a long stop is planned there.

Trains that are marked with (> NWR) can also run via Würzburg-Zell. In this case, if the train should not run via track 4, the route must be set manually on the ESTW panel in Veitshöchheim.

For many freight trains, a staff change (LPW) takes place in Würzburg. The possible stations where this can take place are:
*NWH
*NWZ
*NWR U
*NWR A

The railway yard where a staff change is planned is mentioned in the remarks including an indication of the track, eg NWH LPW 200 of NWR U LPW 505. the relay will call the dispatcher prior to the staff change (exception: early trains or delayed relay; in this case the driver will call). The planned location for staff change is specified in the dialog box. The dispatcher can at that moment choose a different location. In that case, the movement order will be automatically changed.

It often happens that a freight train with a planned staff change in NWR U or NWR A, also makes another short planned stop (usually 2 minutes) in NWH. This is often a stop in which the relieving driver gets on the train or the driver going off duty gets off. In reality, a change in staff is regularly deviated from at Würzburg Hbf. More details for this in the video.

For almost all freight trains, only departure times are specified in the timetable (with the exception of NWR A or NWR U, see [[Dispatching in Zentralstellwerk Würzburg Hbf#Generic Panel NVE/NWR (ESTW)|ESTW]]). This is to prevent freight trains from stopping for a planned stop or operational stop, although the reason for this, e.g. due to a delay, is no longer valid. In case of a staff change (LPW), the stop of the train is automatically executed by the movement order. The dispatcher needs to take care of any other planned or operational stops himself, if necessary. These are stated in the remarks including the planned departure time indicated, for example ''NWH H 04:52 (Halt)'' for operational stops or ''NWH S 00:24 (Stop)'' for requested/planned stops. The train will continue as soon as the exit signal shows proceed.

In Rohrbach, some freight trains also have a stop on the siding of the contra-track. This is specially indicated, for example: ''!!!NRB 804 H 01:05''. Also note that in the track occupation overview only the departure time of the freight train is entered as the transit time and therefore no exact occupation time for the relevant track will be visible.

With the fax option ''„0 Cargo“'' there are no freight trains (exception: freight trains which are subject to shunting operations in NWH or NWR U, eg EX 50000-50007). This is a training mode to become familiar with the passenger traffic. 
With the fax option ''„Cargo+“'' there will be additional freight trains from Wednesday to Sunday, such as engineering trains, single locs as well as empty stock. In this case, it is possible that the dispatcher, even when playing without delays, must make adjustments.

===Generic Panel NVE/NWR (ESTW)===

In order to be able to ensure that freight trains, which run through the area of the Würzburg marshalling yard (NWR) and without the actual neighboring signal boxes being present, can properly run, the railway yards Veitshöchheim (NVE), Würzburg Rbf Ausfahrt (NWR A, only 3 tracks), Würzburg Rbf Zell Umspanngruppe (NWR U) as well as routing into and out of the other parts of the Wurzburg marshalling yard (Rbf 0 to Rbf 3) are operated by an "integrated ESTW". This ESTW can be operated by the dispatcher Würzburg by means of a generic panel.

In the simulation, all trains running here in or through this area are routed through this area by automatic route setting (ARS). The routes are automatically set so that the NWH signal box can be operated by one player. For this purpose, all signals in this area - in contrast to reality - are equipped with ARS. Shunt routes between the Rbf and NWR U, however, must be set manually for both directions.

For NWR U, the boundary of the area of responsibility between the ESTW and NWH lies on the tracks 501-506 and 901-906 respectively. The dispatcher NWH has to set the exit route from the tracks 501-506 for trains towards the Hbf as well as entry routes for the trains from the Hbf towards tracks 501-506. The automatic procedure within the ESTW is only fully guaranteed when the dispatcher routes the trains to the tracks of NWR U as specified in the timetable.

In principle, the tracks 501-506 and 901-906 can be used for both directions, which in reality usually also happens.

In the timetable the tracks 501-503 are used for the direction north-south, and the tracks 504-506 for the direction south-north. There is only one exception for track 503 (direction south-north). Pass-through train traffic always goes via the tracks 501 and 506, a stop can take place on all tracks.

In NWR A only three of the five tracks equipped with overhead lines are displayed on the ESTW. The other two can be reached via the entry tracks to the Rbf. The tracks 604 and 605 are used for pass-through train traffic, track 606 for stops in both directions. Trains terminating or starting in NWR will run via the entry and exit tracks of Rbf. In order to guarantee the automatic operation, all trains that have a scheduled stop in NWR U or NWR A always have a departure and arrival time (exception: Cargo +). This means that the train will always stop, even when it's delayed. For stops within the control area of the ESTW, the route is set about 2 minutes before the scheduled departure time.

When playing with delays, the planned track may be occupied by another train. Here the dispatcher must decide whether the train has to wait or if the train will be routed to another track. For this the route in the ESTW must then be manually set.

For freight trains in the south-north direction, where the staff change (LPW) in Würzburg-Zell takes place on track 3, the auto-fleeting of signal ASiG 40N2 in NVE must be switched off in time, so that ensure that during the LPW no entrance/exit routes to/from NWR will be blocked.

Players who want to avoid the delays that normally occur in goods trains by NWR have the option of always running them on time with the "NWR +0 min" fax option, thus guaranteeing automatic handling at the ESTW.

===Long-distance trains===

All long-distance trains have a short stop in NWH. From Monday to Wednesday, there is one ICE arriving in NWH in the late evening on track 9, and staying there overnight until the next morning's service. On Monday morning this train comes as empty stock from Frankfurt.

Some ICE trains combine or split in NWH. In the event that two trainsets will combine at the platform track, the planned track should be used for this, so that the movement orders will be executed correctly. If another track is used for combining such trains, the movement order for the first train (long entry) must be changed to the correct track.

===Stabling of extra trains===

Some extra trains (see "Overview of extra trains") terminate or start their service in NWH. These trains will be temporarily stabled in stabling area Wasserhaus or in the Gbf.

===Stabling of locomotives===

Locs of DB-Regio are stabled in the railway yard of Drehscheibe 2 or on tracks 260 or 261. Locs of the PbZ trains wait on track 261 until their next service.

The locomotives of private railway operators for freight trains are stabled in the Rbf.

===Stabling of DB Regio-trains===

Most DB Regio trains are stabled on tracks 205, 206, 207, 208, 281 and in the Wasserhaus (Wa) and Talavera (Ta) railway yards. Some train units are stabled on tracks 191, 192 and 465, as well on tracks 456 and 421 near the platforms. A reserve EMU (electric train) is stabled on track 461, which is replaced daily by another train unit.

All regional trains from Frankfurt, which are locomotive-hauled trains, are transferred to the Wasserhaus railway yard by a switcher for cleaning and later stabling. If a train is being stabled on the Wa/Ta yard, the switcher will bring back the train to the platform track for its next service. A train locomotive is usually transferred by the switcher for stabling and also brought back again. For locomotive-hauled trains pulled by 2 locomotives (BR 111), usually one locomotive is stabled near the Drehscheibe 2. But it also happens that both locomotives uncouple or both stay with the train.

For the trains which are stabled on tracks 205-281, the train formation will be carried out on the sidings tracks. For trains which have been transferred to the platform track by the switcher of the Ta/Wa yard, the train locomotive will couple on the platform track.

Diesel trains travel to the tank plate on track 217 before they go to the stabling area. Cleaning can also take place there. Because of the latter, some electric trains also drive to the tank plate.

The following tracks may be used for unscheduled railway trains:
*Track 205 Saturday and Sunday
*Track 206 Monday to Thursday from 11:00 am to 5:00 pm, Saturday from 5:00 am
*Track 208 Monday to Friday from 6:00 am to 4:00 pm, Saturday from 10:00 am
*Track 281 Friday from 12:00, Saturday from 04:00.

===Stabling areas Wasserhaus (Wa) and Talavera (Ta)===

Trains of DB Regio are stabled in both stabling yards. There is a cleaning installation in the Wasserhaus (Wa) yard. That is why all trains go via track 415 to the stabling yard Wa. After cleaning, the train is then stabled on a stabling track. Trains that have been stabled in the vicinity of the Hbf are returned via track 415 of the stabling yard Wa. In order to stable a train in the Talavera (Ta) yard, the dispatcher must set a shunt route from track 413 to track 403. These trains are later brought back via this same track 403 for a new service.

Since all train movements out of the stabling area Wa/Ta (tracks 415, 413 and 403) are not shown in the train overview or in the timetable, these movements are mentioned in the list "Train movements from Wa/Ta".

Trains marked with AAT (AppearsAfterTrain) depend on the arrival time of the train mentioned in the right-hand column. If that train is delayed, the start time of the corresponding transfer from Wa/Ta will increase by as much time.

In the case of train movements from the Hbf to track 415, there must be sufficient time until the moment a movement out of Wa will take place. In case of doubt, the arrived train stays on the platform longer. Normally there is sufficient room for this. Only the ICE/IC tracks 4-7 must be cleared relatively quickly.

===Switchers===

The switcher of DB Regio is normally located at the stabling area Wa/Ta. However, in case of short intervals between two movement orders the switcher will be stabled on track 423 in the vicinity of the platforms.

The handling of the PbZ-D 2487 and the formation of the wagons of RE 4627 overlap. In reality, these trains are treated successively by the switcher of DB Regio. When playing with delays, ans so the order of the trains and the time interval can strongly vary, different scenarios of the handling by the switcher are conceivable. However, they can not all be included in the timetable. Therefore, on the days that PbZ-D 2487 is running, two switchers will appear in succession from the stabling area Wa.

For the train formation of the DHL express trains (EX 5000-50006) a switcher with personnel of the Rbf will come to the Gbf in NWH. If this locomotive is not used for service, it goes to track 217 to refuelling.

The transfer of freight wagons from Rbf to the port and back is carried out by a switcher of a private railway company located in the port area. The scrap dealer is served by a DB Cargo locomotive.

===PbZ-D trains===

In Würzburg a train pair runs once a week as PbZ-D between Munich and Leipzig. Usually the service day is on a Thursday, in the summer of 2016 on Tuesday, and in the autumn of 2016 on both days.

The exact periods are as follows:

''PbZ-D 2486''
*Thu: until 31-03-2016 and from 05-10-2016, also on 19.05.2016
*Tue: 01-03-2016 until 06-12-2016, not on 08-/15-/29-03-2016 as well as on 17-05-2016

''PbZ-D 2487''
*Thu: until 31-03-2016 and from 06-10-2016
*Tue: 05-04-2016 - 27-09-2016 and 06-10-2016 - 08-12-2016

In the timetable, wagons are added or removed for all these trains by the switcher (Ta/Wa).

In reality, the PbZ-D trains are running with very varying train compositions and are also handled as such in NHW. To take this into account, other scenarios can be selected by fax. More details can be found in the ''„[[Dispatching in Zentralstellwerk Würzburg Hbf#Overview of PbZ-D trains|Overview of PbZ-D trains]]“.

===Turning around at the east side===

The tracks on the east side are divided into two groups: Ost L and Ost K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. However, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

For group Ost L it should be noted that there are restrictions for track 468:
*Only the platform tracks 5-11 can be reached from this track.
*Only single unit EMU/DMU trains or locomotives can turn around on this track.
*On this track, certain DMU units are temporarily stabled until their next service.

===Turning around at the west side===

The tracks on the east side are divided into two groups: West L and West K (see track overview).

In the Remarks, the group or a specific track is mentioned. The movement orders are all written in such a way that the dispatcher can always use any track in the relevant group for turning around. Exceptions are the movements to and from the refueling station. Track 391 should always be used here. Additionally, when choosing a particular track, care must be taken to see whether the final destination track can be reached from there.

There is a separate group of tracks assigned for the turn around for entering/leaving into/from Talavera and Wasserhaus.

=== Additional remarks in the train overview window===

Movement orders in brackets mean that these movement orders will be executed, but not by this train. This is often the case for trains waiting at the platform or in the stabling area, waiting to combine with an other train.

The sign ''^xxx'' means that the train will be overtaken by train xxx. Trains with the note ''„SFS GWB!! ^xxx/yyy/zzz“'' have to be send onto the SFS planned via the contra-track (GWB) towards Burgsinn. This is the case, for example, for the diverted ICE trains (Nürnberg-Leipzig) where the diverted train is overtaken by the regular ICE into the direction of Burgsinn.

For EMU/DMU/locs that drive to the refueling station on track 217, it is stated whether they are being cleaned (EMU) or refueled (DMU/locs). The required time is about 10 minutes per carriage. Each time, the time required is to be determined by the dispatcher himself. For the RAbt 23552, only the front car will be refueled. The last carriage will drive the stabling track 192 to the tank plate just before its next service.

===Movement orders===

All movement orders, which are to be carried out on the platform tracks, do not have a fixed track assigment. As a result, the dispatcher can act flexibly if necessary, and the movement orders are also carried out when the train is sent to another track.

Exceptions here are movement orders for a long entry routes to the second track section of a platform track. Here the exact track is given so that the train does not stop on the first track section. If such trains are sent to another track, the movement order must be changed in time.

For a short entry route, the dispatcher must set the train route up to the cover signal. Shunt movements with a short entry route automatically stop at the first section of the platform track. The same applies to train movements where only one track section of a platform track is mentioned in the comments.

=== Stabled trains at program start ===

When starting a simulation, certain locomotives, cars or complete trains will be stabled on the tracks where they should be located at that time in accordance with the timetable.

This could be trains, which have arrived recently and are to be combined with an arriving train which is scheduled to arrive after the start of the simulation. When playing with delays, it may happen that an already stabled train shows up again as a delayed train. Since the delays are randomly generated in the simulation, it is impossible to take this into account. For such cases, the delayed train should be cancelled.

The same could happen for trains stabled in the stabling yards. Please check the list of stabled trains at program start (by means of the notepad) and check the announced trains with their remarks closely.

===Rescue train===

A rescue train is continuously stabled on track 209. This train can make a condition ride on Tuesday. For this purpose, the train must be occupied with personnel by 08:30 using the „movement orders“ window. After a short time the train will change its train number and can depart from track 209, according to the timetable, towards the SFS. Of course, the train can also be manned on any other day and at any other time. The train number will always change then. However, a timetable for this train is only scheduled on Tuesdays (departure: 8:42 am).

In order to ensure that the rescue train returns from the condition ride later on, the fax option „RTZ“ must be activated in time before 10:32 am. This option can be used from Monday to Friday, in case the dispatcher decides to let the condition ride take place on another day.

=== Additional traffic (Zusatzverkehr) ===

In order to offer even more variety in train traffic, additional (unplanned) train traffic has been set up in various ways.

*Various football specials (see "Overview of extra trains")
*Every Tuesday, the EK 56875 carries a wagon with axles for the workshop of DB Regio in Talavera.
*Some diesel locomotives go to track 217 during their deployment to refuel.

Other extra trains can be activated at any time using the fax option ''„Cargo +“''.

== Overview of the handling of PbZ-D trains==

Below an overview of the handling of the PbZ-D trains. The required actions for the dispatcher are stated in the remarks of the relevant RLok/RAbt (switcher). The switcher appears depending on the arrival of the PbZ-D train. This train always goes to track 205.

In the timetable, wagons are added to or uncouple from all trains using by a switcher. For the PbZ-2487 (arriving late in the evening), the switcher will place the required wagons on track 435 during the day. This is included in the timetable as the variant („Regel“).

Other variants can be selected by fax (to be activated in time before the planned arrival of the PbZ-D). The variants have the following meaning:

{| cellpadding="10" cellspacing="0" border="0"
|-
| A: Thursday || B: Tuesday ||  
|-
| 2: only uncoupling wagons || 1: only adding wagons || 0: no handling
|}

{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Train-Nr.''' || '''Variant''' || '''arr''' || '''Handling''' || '''dept'''
|-
| 2486 || Regel || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings a wagon from Wa and couples it on the front side
*Switcher runs around and uncouple the last wagon
*Switcher brings the car towards Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 2 || 00:57 ||
*Last wagon will be uncoupled
*Switcher comes out of Wa via the eastside, and couples with the wagon
*Switcher transfers the wagon to Wa via the eastside
|| 01:53

|- style="vertical-align:top;"
| 2486 || 1 || 00:57 ||
*Train loc uncouples and waits on track 261
*Switcher brings wagons from Wa and couples them on the front side
*Switcher returns to Wa
*Train loc couples on the front side
|| 01:53

|- style="vertical-align:top;"
| 2486 || 0 || 00:57 ||
*PbZ-D will continue with the same train composition
|| 01:53

|- style="vertical-align:top;"
| 2487 || Regel || 22:17 ||
*14:01 Switcher transfers wagons to track 435, and stables them there

*Switcher comes out of Wa, and couples to the back of the train
*Switcher transfers uncoupled wagons as RAbt to track 435
*RAbt couples with the stabled cars on track 435
*RAbt couples again with the PbZ train
*Switcher uncouples cars to be stabled and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 2 || 22:17 ||
*Last wagons are uncoupled
*Switcher comes out of Wa and couples with those cars
*Switcher transfers the wagons to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 1 || 22:17 ||
*Switcher comes out of Wa with wagons, and couples them to the back of the train
*Switcher uncouples and goes back to Wa
|| 23:13

|- style="vertical-align:top;"
| 2487 || 0 || 22:17 ||
*PbZ-D continuous its service with the same train composition
|| 23:13

|}

When selecting a variant by fax, the wagons being stabled during daytime are stabled on track 435. Anyone who wants to, can change the movement orders of the switcher (RLok) and have these wagons transferred to stabling area Wa after having completed the train composition of the PbZ-D train.

Periods for the individual traffic days:

{| cellpadding="10" cellspacing="0" border="0"
|- style="vertical-align:top;"
| PbZ-D 2486 || Thu (A): Tue (B): || until 31/03/2016 and from 05/10/2016, additionally on 19/05/2016 01/03/2016 – 06/12/2016, not on 08, 15, 29/03/2016 and 17/05/2016

|- style="vertical-align:top;"
| PbZ-D 2487 || Thu (A): Tue (B): || until 31/03/2016 and from 06/10/2016 05/04/2016 – 27/09/2016 and 06/10/2016 – 08/12/2016

|}

== List of extra trains ==

Football Specials Würzburger Kickers
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time at platform''' || '''Match''' || '''Play time'''
|-
| 6-2-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-VfB Stuttgart II || 14:00-16:00
|-
| 6-2-2016 || Würzburg Hbf || Stuttgart Hbf || 18:00-18:15 || Würzb.-VfB Stuttgart II || ---
|-
| 1-3-2016 || Würzburg Hbf || Halle || 12:30-13:00 || Halle - Würzburg || 19:00-21:00
|-
| 2-3-2016 || Halle || Würzburg Hbf || 1:00-1:45 || Halle - Würzburg || ---
|-
| 18-3-2016 || Köln Hbf || Würzburg Hbf || 16:30-17:00 || Würzb.-Fortuna Köln || 19:00-21:00
|-
| 18-3-2016 || Würzburg Hbf || Köln Hbf || 22:45-23:30 || Würzb.-Fortuna Köln || ---
|-
| 2-4-2016 || Würzburg Hbf || Osnabrück Hbf || 7:15-8:00 || Osnabrück - Würzb. || 14:00-16:00
|-
| 2-4-2016 || Osnabrück Hbf || Würzburg Hbf || 23:45-00:20 || Osnabrück - Würzb. || ---
|-
| 9-4-2016 || Stuttgart Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Stuttg. Kickers || 14:00-16:00
|-
| 9-4-2016 || Würzburg Hbf || Stuttgart Hbf || 17:15-17:45 || Würzb.-Stuttg. Kickers || ---
|-
| 23-4-2016 || Rostock Hbf || Würzburg Hbf || 12:00-12:30 || Würzb.-Hansa Rostock || 14:00-16:00
|-
| 23-4-2016 || Würzburg Hbf || Rostock Hbf || 17:45-18:15 || Würzb.-Hansa Rostock || ---
|-
| 7-5-2016 || Kiel Hbf || Würzburg Hbf || 11:40-12:00 || Würzb.-Holstein Kiel || 13:30-15:30
|-
| 7-5-2016 || Würzburg Hbf || Kiel Hbf || 16:00-16:45 || Würzb.-Holstein Kiel || ---
|-
| 14-5-2016 || Würzburg Hbf || Magdeburg Hbf || 8:30-9:00 || Magdeburg-Würzburg || 13:45-15:45
|-
| 14-5-2016 || Magdeburg Hbf || Würzburg Hbf || 19:45-20:15 || Magdeburg-Würzburg || ---
|-
| 14-8-2016 || Kaiserslautern || Würzburg Hbf || 12:00 || Kaiserslautern - Würzb. || ---
|-
| 14-8-2016 || Würzburg Hbf || Kaiserslautern || 17:00 || Kaiserslautern - Würzb. || ---
|-
| 25-9-2016 || Würzburg Hbf || Dresden Hbf || 07:30 || Dynamo Dresden-Würzb. ||
|-
| 25-9-2016 || Dresden Hbf || Würzburg Hbf || 20:00 || Dynamo Dresden-Würzb. ||
|-
| 30-10-2016 || Würzburg Hbf || Hannover Messe Laatzen || 07:45 || Hannover 96 - Würzb. ||
|-
| 30-10-2016 || Han Messe Laatzen || Würzburg Hbf || 18:00 || Hannover 96 - Würzb. ||
|}

Football Specials 1. Bundesliga
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Date''' || '''Origin''' || '''Destination''' || '''Time''' || '''Match'''
|-
| 5-3-2016 || München Hbf || Dortmund Signal Iduna Park || 12:03 || BVB - FCB
|-
| 6-3-2016 || Dortmund Signal Iduna Park || München Hbf || 01:15 || BVB - FCB
|-
| 19-3-2016 || München Hbf || Köln Deutz Tief || 08:00 || 1. FC Köln - FCB
|-
| 19-3-2016 || Köln Deutz Tief || München Hbf || 22:30 || 1. FC Köln - FCB
|-
| 21-5-2016 || München Hbf || Berlin Hbf || 11:49 || BVB - FCB
|-
| 22-5-2016 || Berlin Hbf || München Hbf || 03:14 || BVB - FCB
|-
| 24-9-2016 || München Hbf || Hamburg Altona || 07:30 || Hamburger SV - FCB
|-
| 24-9-2016 || Hamburg Altona || München Hbf || 23:45 || Hamburger SV - FCB
|-
| 15-10-2016 || München Hbf || Frankfurt Stadion || 11:15 || Eintracht Frankf.-FCB
|-
| 15-10-2016 || Frankfurt Stadion || München Hbf || 19:30 || Eintracht Frankf.-FCB
|-
| 19-11-2016 || München Hbf || Dortmund Signal Iduna Park || 12:17 || BVB -FCB
|-
| 20-11-2016 || Dortmund Signal Iduna Park || München Hbf || 01:39 || BVB -FCB
|}

{{EnglishNavBottom}}

Contents:Extensions

2017-03-20T21:29:11Z

Charlie: /* Pages in development */

{{DeveloperNav}}

=General=
*[[Command Line Options|Command Line Options]]
*[[Timetables|Legacy Timetable Editing/Creation using MS Access]]
*[[SimSchedule|Current Timetable Editing/Creation using SimSchedule]]
*[[Scenarios|Scenario Creation]]
*[[Installers|Developing Installers]]
*[[Defects|Information about defect types and their probabilities of occurring]]

=Software Development Kits=
On the pages listed below you will find detailed technical information like track sections, track lengths, station definitions, switch names, signal names, spawning points and so on for the individual simulations available. This information could be very useful to those people who like to develop their own timetables and/or scenarios.

==SDK's for the Dutch GRS-NX panels==
*[[SDK:Hengelo|SDK for the Hengelo Simulation]]
*[[SDK:Amsterdam CS|SDK for the Amsterdam CS Simulation]]

==Pages in development==

[[Örtliche Kenntnisse für Stellwerk Mülheim(Ruhr)-Styrum]] / [[Dispatching in Stellwerk Mülheim(Ruhr)-Styrum]] / [[Plaatselijke bekendheid in Stellwerk Mülheim(Ruhr)-Styrum]]

[[Örtliche Kenntnisse für Zentralstellwerk Oberhausen Hbf]] / [[Dispatching in Zentralstellwerk Oberhausen Hbf]] / [[Plaatselijke bekendheid in Zentralstellwerk Oberhausen Hbf]]

[[Örtliche Kenntnisse für Zentralstellwerk Würzburg Hbf]] / [[Dispatching in Zentralstellwerk Würzburg Hbf]] / [[Plaatselijke bekendheid in Zentralstellwerk Würzburg Hbf]]

[[Örtliche Kenntnisse für Stellwerk Burgsinn Bbf]] / [[Dispatching in Stellwerk Burgsinn Bbf]] / [[Plaatselijke bekendheid in Stellwerk Burgsinn Bbf]]

[[Örtliche Kenntnisse für Stellwerk Gemünden (Main)]] / [[Dispatching in Stellwerk Gemünden (Main)]] / [[Plaatselijke bekendheid in Stellwerk Gemünden (Main)]]

[[Örtliche Kenntnisse für Stellwerk Jossa]] / [[Dispatching in Stellwerk Jossa]] / [[Plaatselijke bekendheid in Stellwerk Jossa]]

[[Örtliche Kenntnisse für Stellwerk Flieden]] / [[Dispatching in Stellwerk Flieden]] / [[Plaatselijke bekendheid in Stellwerk Flieden]]

[[Örtliche Kenntnisse für Stellwerk Neuhof]] / [[Dispatching in Stellwerk Neuhof]] / [[Plaatselijke bekendheid in Stellwerk Neuhof]]

[[Örtliche Kenntnisse für Stellwerk Würzburg Heidingsfeld]] / [[Dispatching in Stellwerk Würzburg Heidingsfeld]] / [[Plaatselijke bekendheid in Stellwerk Würzburg Heidingsfeld]]

[[Örtliche Kenntnisse für Stellwerk Ochsenfurt]] / [[Dispatching in Stellwerk Ochsenfurt]] / [[Plaatselijke bekendheid in Stellwerk Ochsenfurt]]

[[Örtliche Kenntnisse für Stellwerk Mannheim Hbf]] / [[Dispatching in Stellwerk Mannheim Hbf]] / [[Plaatselijke bekendheid in Stellwerk Mannheim Hbf]]

[[Örtliche Kenntnisse für Stellwerk Ludwigshafen (Rhein) Hbf]] / [[Dispatching in Stellwerk Ludwigshafen (Rhein) Hbf]] / [[Plaatselijke bekendheid in Stellwerk Ludwigshafen (Rhein) Hbf]]

[[Örtliche Kenntnisse für Stellwerk Hamburg Hbf]] / [[Dispatching in Stellwerk Hamburg Hbf]] / [[Plaatselijke bekendheid in Stellwerk Hamburg Hbf]]

[[Örtliche Kenntnisse für Stellwerk Obertraubling]] / [[Dispatching in Stellwerk Obertraubling]] / [[Plaatselijke bekendheid in Stellwerk Obertraubling]]

[[Örtliche Kenntnisse für Stellwerk Landshut Hbf]] / [[Dispatching in Stellwerk Landshut Hbf]] / [[Plaatselijke bekendheid in Stellwerk Landshut Hbf]]

[[Örtliche Kenntnisse für Stellwerk Karlsruhe-Durlach]] / [[Dispatching in Stellwerk Karlsruhe-Durlach]] / [[Plaatselijke bekendheid in Stellwerk Karlsruhe-Durlach]]

[[Örtliche Kenntnisse für Stellwerk Haiger]] / [[Dispatching in Stellwerk Haiger]] / [[Plaatselijke bekendheid in Stellwerk Haiger]]

Örtliche Kenntnisse für Stellwerk Herzogenrath

2017-03-20T15:15:06Z

Charlie:

{{GermanNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Stellwerk Herzogenrath|EN=Dispatching in Stellwerk Herzogenrath|NL=Plaatselijke bekendheid in Stellwerk Herzogenrath}}
{{GermanConstruction}}

Bevor Sie zum ersten Mal auf einem Stellwerk Dienst schieben, müssen Sie sich mit den Örtlichkeiten vertraut machen und über die Besonderheiten informieren. Nach der allgemeinen Ausbildung zum Stellwerkswärter wurden die angehenden Fahrdienstleiter immer wochenlang neben einen Fachmann auf dem Stellwerk eingesetzt. Dieses Kapitel ist diese erste Einweisung für Sie als Fahrdienstleiter. Lesen Sie es sorgfältig durch. Es enthält sehr wichtige Angaben aus der Praxis.

Der Text ist von “Kollege zu Kollege” geschrieben, als ob Sie auf dem Stellwerk sind, den ersten Tag nach der Ausbildung.

[https://signalsimulation.com/zoom/herzogenrath Das Sp Dr S 600-Zentralstellwerk Herzogenrath im Überblick]

== Stellwerk Herzogenrath ==

===Grundlagen===
Hallo und Herzlich willkommen auf deiner ersten Schicht auf dem Stellwerk Herzogenrath (Hf). Ich bin der Sebastian und werde dich zunächst einmal mit den grundlegenden Gegebenheiten hier vertraut machen. Später werfen wir dann noch einen genauen Blick auf die einzelnen Bereiche auf unsererm Stelltisch.

Unser Stellwerk vom Typ Dr S 600 wurde 1985 in Betrieb genommen. Davor wurde der Bahnhof von 2 mechanischen Stellwerken bedient, die mit dem Bau des Relaisstellwerks überflüssig wurden.
Ebenso wurden in benachbarten Betriebsstellen Änderungen vorgenommen, wie die Umrüstung auf Fernsteuerbetrieb des Bahnhof Kohlscheid, dazu aber später mehr.

Das Verkehrsaufkommen ist in unserem Bereich nicht sehr hoch, sodass du dich sehr schnell mit den Örtlichkeiten vertraut machen kannst.

===Die Strecken===
Unser Stellwerk liegt an folgenden drei Strecken:
*2543 Herzogenrath Grenze - Herzogenrath
*2550 Aachen - Kassel
*2570 Stolberg - Herzogenrath (Ringbahn)

===Die Nachbarn===
====Strecke Landgraaf - Herzogenrath (gelbe Strecke)====
Die Strecke von Landgraaf nach Herzogenrath ist eine grenzüberschreitende Strecke in die benachbarten Niederlande. Die nächsten Betriebsstellen sind hier Landgraaf und Heerlen. Sie ist nicht elektrifiziert und wird regelmäßig von Dieseltriebwagen der Br 642 befahren. Unser Nachbar ist hier der Fahrdienstleiter in Landgraaf.
Als Zugmeldeverfahren wird hier noch auf das Anbieten per Telefon zurückgegriffen.

[[File:KHEZ_Landgraaf.png|none|Landgraaf|760px]]

====Strecke Stolberg - Herzogenrath (braune Strecke====
Die Strecke von Stolberg nach Herzogenrath ist ein Teil der Ringstrecke um Aachen. Sie endet derzeit in Eschweiler St.Jöris welches auch der Endpunkt dieser Strecke ist. Sie ist nicht elektrifiziert und wird regelmäßig von Dieseltriebwagen der Br 642 befahren. Unser Nachbar ist hier der Fahrdienstleiter Stolberg.
Auf das Zugmeldeverfahren wird hier verzichtet da sich immer nur ein Zug auf der Strecke befindet.
[[File:KHEZ_Eschweiler.png|none|Eschweiler|660px]]

====Strecke Aachen - Kassel (grüne Strecke)====
Das elektronische Stellwerk (ESTW) Geilenkirchen übernahm 2006 die Steuerung des Streckenabschnitts zwischen Herzogenrath und Rheydt. Hierbei wurde aus dem Bahnhof Übach-Palenberg ein Haltepunkt gemacht, an dem die Personenzüge aus beiden Richtungen her halten können.
Diesen können wir auf der linken Seite der Wand sehen (Gleis 9003 sowie 9004).
Links verbindet sich die Strecke mit dem Bahnhof Geilenkirchen, unser Nachbar ist hier der Fahrdienstleiter Geilenkirchen. Auf beiden Gleisen ist GWB eingerichtet.
Als Anbietefelder sind das Feld A9232 für Fahrten im Gegengleis nach Geilenkirchen sowie das Feld A9003 für Fahrten auf dem Gegengleis aus Richtung Geilenkirchen eingerichtet.
[[File:KHEZ_Geilenkirchen.png|none|Geilenkirchen|760px]]

Auf der rechten Seite befindet sich die Strecke in Richtung Aachen West. Als nächste Betriebsstelle folgt hier die Überleitstelle Richterich, die dem Fahrdienstleiter in Aachen West zugeordnet ist.
Auf beiden Gleisen ist GWB eingerichte.Als Anbietefeld sind das Feld A151 für Fahrten auf dem Gegengleis zur Üst Richterich und das Feld A171 auf dem Gegengleis aus Richtung Üst Richterich eingerichtet.
[[File:KHEZ_Richterich.png|none|Richterich|760px]]

===Die Betriebsstellen===

====Bahnhof Kohlscheid====
Der Bahnhof Kohlscheid wird von Herzogenrath aus Ferngesteuert. Hier steht vor Ort ein Dr S600 Stellwerk.
In der Regel läuft der Bahnhof Kohlscheid alleine im Selbststellbetrieb. Regionalzüge halten hier gelegentlich, in der Regel solche mit der Relation Aachen - Eschweiler St.Jöris oder nach Landgraaf. Alle anderen Züge fahren hier durch.
Aufpassen solltest du hierbei wenn du von Kohlscheid aus ins Gegengleis Richtung Aachen West fahren möchtest. Da dir eine Weichenverbindung fehlt musst du du bereits ab Herzogenrath im Gegengleis fahren.
[[File:KHEZ_Kohlscheid.png|none|Kohlscheid|760px]]

===== Übersicht der Fahrstraßenziele Kohlscheid =====
 
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Beschreibung''' || '''Ziel'''
|-
| Kohlscheid - Herzogenrath Regelgleis || 172II
|-
| Kohlscheid - Herzogenrath Gegengleis || 152I
|-
| Kohlscheid - Üst Richterich Regelgleis || 171I
|-
| Kohlscheid - Üst Richterich Gegengleis || 151I
|}
 

====Bahnhof Herzogenrath====
Der Bahnhof Herzogenrath besitzt an den Esig A805 sowie F860 sowie an den Asig N1 und P2 Selbststellbetrieb. Dieser ist jedoch nicht besonders gut zu gebrauchen, da dieser Züge nur auf dem Hauptgleis fahren lässt und du oft eingreifen musst.
Es gibt insgesamt 4 Bahnsteige, in Gleis 55, Gleis 1 sowie 2 und 3.
Gleis 55 wird für endende Dieseltriebwagen benutzt, da das Gleis nicht mit Oberleitung überspannt ist.
Gleis 1, 2 und 3 können von haltenden Regionalzügen benutzt werden. Hierbei musst du nur beachten, dass Züge aus Richtung Eschweiler St. Jöris nur nach Gleis 1 oder 3 einfahren können, da es sich bei der Weiche 095 nur um eine Flachkreuzung handelt.

Die beiden Stumpfgleise 059 und 075 sind "draußen" nicht mehr vorhanden, deswegen sind die Gleise dauerhaft gesperrt.
Die Stumpfgleise 012 bis 015 sind aufgrund von Oberbaumängeln ebenfalls dauerhaft gesperrt, dort wachsen Bäume zwischen den Schwellen.

[[File:KHEZ_Herzogenrath.png|none|Herzogenrath|760px]]

===== Übersicht der Fahrstraßenziele Herzogenrath =====
 
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Beschreibung''' || '''Ziel'''
|-
| nach Eschweiler St. Jöris || F,yyy.890II
|-
| nach Geilenkirchen Regelgleis || 880II
|-
| nach Geilenkirchen Gegengleis || 860II
|-
| nach Landgraaf || F,yyy.890II
|-
| Herzogenrath - Kohlscheid Regelgleis || 850
|-
| Herzogenrath - Kohlscheid Gegengleis || 803
|}
 
=== Abweichende S600 Befehle ===
Für die Signale und Weichen im Bahnhof Herzogenrath werden, abweichend der Weichen- und Signalbezeichnung im Tischfeld andere Befehle für die DET verwendet:
Beispielsweise wird das Signal im Tischfeld als P001 bezeichnet, als DET Befehl wird jedoch nur P1 benutzt.
Gleiches gilt für Weichen, hierbei wird aus Weiche 001 nur die Weiche 1.
Es gilt also, dass die vorangestellten Ziffern " '''0''' " für Befehlseingabe in der DET entfernt werden müssen.
Als Hilfe wird beim Bewegen der Mauszeiger über ein Signal ggf. in Klammern die Bezeichnung für die DET gezeigt. Z.B. -> N055 (N55), wobei dann die N55 die Angabe fuer die DET ist.

===== Übersicht der zusätzlichen Zieltasten Herzogenrath =====
 
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''(Start)/Ziel''' || '''Beschreibung'''
|-
| .N1P || gerader D-Weg mit Vmax Richtung Übach Palenberg
|-
| .N1 || D-Weg nach rechts mit Vmax 60
|-
| .P2L || langer D-Weg mit Vmax
|-
| .P2 || kurzer D-Weg mit Vmax 60 bis vor W4
|-
| .P3L || langer D-Weg auf die Hauptstrecke
|-
| .P3 || kurzer D-Weg bis vor W6
|}
 

===Besonderheiten===
====Anrückmelder====
Aufgrund der langen Entfernung zwischen Eschweiler St. Jöris und unserem Einfahrsignal G890 ist hier eine Anrückmelder installiert. Dieser fängt an rot zu blinken wenn sich der Zug dem Esig G890 nähert. Für dich ist dies ein Zeichen, dem Zug die Einfahrt zu stellen.
[[File:KHEZ_Anrueckmelder_aktiv.png|none|Anrueckmelder|760px]]
Hast du dem Zug die Einfahrt gestellt, hört der Melder auf zu blinken.
[[File:KHEZ_Anrueckmelder_aus.png|none|Anrueckmelder|760px]]

====Tastensperrmelder====
Der Tastensperrmelder hat folgende Aussagen:
*dunkel: wenn eine Fahrstraße mit den Signaltasten an der Stellwand eingestellt wird
*rot leuchtend: es findet eine Bedienung per DET statt oder der Selbststellbetrieb stellt gerade eine Fahrstraße ein
*rot blinkend: es wurde eine Bedienhandlung durchgeführt, die von der Anlage nicht ausgeführt werden konnte (z.B. das Umstellen einer besetzten/Verschlossenen Weiche mit WGT)
Es ist jeweils ein Melder für den Bereich Herzogenrath sowie für den Bereich Kohlscheid angebracht.

[[File:KHEZ_Tastensperrmelder.png|none|Tastensperrmelder|242px]]

====zusätzliche Zählwerke====
Zusätzlich zu dem vorhandenen Störungsdrucker, der jede Hilfshandlung registriert sind zwei zusätzliche Zählwerke vorhanden. Diese Arbeiten auch bei Ausfall des Störungsdruckers und sind wie folgt dargestellt:
*Weichengesamtzählwerk - WGZ: zeichnet alle zählwerkspflichtigen Bedienhandlungen der Weichentasten auf.
[[File:KHEZ_WGZ.PNG|none|Weichengesamtzählwerk|241px]]

*Signal- und Fahrstraßengesamtzählwerk - SFGZ: zeichnet alle zählwerkspflichtigen Bedienhandlungen der Signal- und Fahrstraßentasten auf.
[[File:KHEZ_SFGZ.PNG|none|Signal- und Fahrstraßengesamtzählwerk|242px]]

====zusätzliche Melder - Stellwerk Kohlscheid====
Da es sich bei dem Stellwerk Kohlscheid um ein ferngesteuertes Stellwerk handelt, sind hier zusätzliche Melder verbaut die Aussagen über den Zustand der Signale/Weichen der ferngesteuerten Anlage anzeigen.
*Melder '''S''' (Signalstörmelder) zeigt an, dass im Bereich des Stellwerks Kohlscheid ein Signal erloschen ist
*Melder '''SFL''' (Signalfehlermelder) zeigt an, dass im Bereich des Stellwerks Kohlscheid der Hauptfaden eines Signals erloschen ist
*Melder '''W''' (Weichenstörmelder) zeigt an, dass im Bereich des Stellwerks Kohlscheid eine Weichenstörung vorliegt
*Melder '''Ers''' (Ersatzsignalkontrollmelder) zeigt Ruhelicht, wenn im Bereich des Stellwerks Kohlscheid kein Signal Zs1 oder Zs7 leuchten. Leuchtet ein Signal Zs1 oder Zs7 fängt der Melder an zu blinken.
Die ertönende Hupe bei Signalstörung oder Wecker bei Weichenstörung werden mit den Tasten '''HUT''' und '''WUT''' im Bereich der grauen Gruppentasten abgeschaltet
[[File:KHEZ_Ers.PNG|none|Ersatzsignalkontrollmelder|242px]] (zusätzlich Bild HUT + WUT)

====Fernsteuerbetriebsmelder====
Aufgrund der fehlenden Spurausleuchtung im Bahnhof Kohlscheid ist hier ein Fernsteuerbetriebsmelder vorhanden. Dieser Melder gibt dir eine optische Rückmeldung, ob dein Fahrstraßenbefehl vom Stellwerk Kohlscheid ausgeführt wurde. Dabei haben die Melder folgende Aussagen:
*FGrM leuchtet: es findet keine Veränderung im Stellbereich des Stellwerks Kohlscheid statt.
*FBM leuchtet: es findet eine Veränderung im Stellbereich des Stellwerks Kohlscheid statt. Es wird z.B. eine Fahrstraße eingestellt oder ein Gleisabschnittes wird durch eine Zug- oder Rangierfahrt besetzt oder freigefahren.
Dabei ist zu beachten: der Melder "FBM" und "FGrM" blinken bei einer Veränderung im Bereich Kohlscheid immer im Wechsel.
[[File:KHEZ FGRM.png|none|Fernsteuerbetriebsmelder|242px]]

====Tischfelder Weichen====
Im Bahnhof Kohlscheid ist die Darstellung der Tischfelder der Weichen abweichend von denen im Bereich Herzogenrath:
*fehlender Spitzenmelder
*Stellungs- und Überwachungsmelder blinkt, bei einem Umstellvorgang so lange in seiner alten Position bis die Weiche ihre neue Endlage erreicht hat und geht dann in Ruhelicht über.
[Bild Weichen]

====Meldeprüfung====
Da es sich beim Stellwerk Kohlscheid um ein ferngesteuertes Stellwerk handelt und hier die Gleisabschnittsmelder im Grundzustand dunkel sind ist eine zusätzliche Einrichtung verbaut.
Diese nennt sich Meldeprüfung und wird bei Fahrten mit Signal Zs1 gebraucht. Hierbei wird mit Hilfe von folgenden Bedienhandlungen das Freisein der sonst dunklen Gleisabschnitte festgestellt:
*1. MPr + Bahnhofstaste: alle Gleisabschnittsmelder, StüM und Signale werden "gelöscht" und dunkel angezeigt
*2. MPr + Bahnhofstaste: alle Gleisabschnittsmelder und StÜM werden gelb ausgeleuchtet, wenn diese nicht besetzt sind, Signale zeigen ihren normalen Halt/Fahrtbegriff
*3. MPr + Bahnhofstaste: alle Gleisabschnittsmelder werden dunkel angezeigt, StÜM werden dunkel angezeigt es sei denn sie sind in einer Fahrstraße beansprucht, Signale zeigen ihren normalen Halt/Fahrtbegriff
[Bild MPr]

==Übersicht Anbieten von Züge über DET==

Mehr Information : [[Kontrollmonitor Sp Dr S 600|Kontrollmonitor und DET]]

{{OfferingTrainsDET:TableDetailsKHEZ|DE}}

==Abkürzungen==

[[File:Line_Herzogenrath.png|586px|thumb|none|Herzogenrath : im Fahrplan verwendete Ziele]]

{{ShortNames:TableDetailsKHEZ|DE}}

== Gleislängen / Durchfahrgeschwindigkeiten ==

{{TrackLengths:TableDetailsKHEZ|DE|Herzogenrath}}
{{TrackLengths:TableDetailsKKOS|DE|Kohlscheid}}

{{Autofleet:TableDetailsKHEZ|DE}}

{{GermanNavBottom}}

Dispatching in Stellwerk Herzogenrath

2017-03-20T15:14:42Z

Charlie:

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Stellwerk Herzogenrath|EN=Dispatching in Stellwerk Herzogenrath|NL=Plaatselijke bekendheid in Stellwerk Herzogenrath}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is the brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [https://signalsimulation.com/zoom/herzogenrath/ Sp Dr S 60-Stellwerk Herzogenrath panel] here.

== Stellwerk Herzogenrath==

===Lines===
Our signalbox is located along the following 3 lines:
*2543 Herzogenrath Grenze (border) - Herzogenrath
*2550 Aachen - Kassel
*2570 Stolberg - Herzogenrath (Ringbahn)

===Neighbouring Dispatching Areas===
====Line Landgraaf - Herzogenrath (yellow line)====
The line from Herzogenrath towards Landgraaf is a cross-border route towards the Netherlands. The station there are Landgraaf and Heerlen. It is a non-electrified line and is regularly serviced by diesel multiple unita (DMU) of the series BR 642. Our neighbouring dispatcher here is the dispatcher in Landgraaf.
All trains need to offered to the neighbour prior to sending it out.

[[File:KHEZ_Landgraaf.png|none|Landgraaf|760px]]

====Line Stolberg - Herzogenrath (brown line)====
The line from Stolberg to Herzogenrath is a part of the circle line around Aachen. It currently ends in Eschweiler St.Jöris, which is also the end point for services on of this route. It is a non-electrified line and is regularly service by BR ^42 DMU's. Our neighbour here is the dispatcher of Stolberg.
Offering trains is omitted here, as one train at the time may be on this line.
[[File:KHEZ_Eschweiler.png|none|Eschweiler|660px]]

====Line Aachen - Kassel (green line)====
The electronic signal box (ESTW) Geilenkirchen took over de control of the section between Herzogenrath and Rheydt. At that same moment, the station of Übach-Palenberg was changed into a simple halt, where trains from both directions could have their stop.
We can see this on the left side of the panel (tracks 9001 and 9004).
On the left side, the line connects us with the station of Geilkirchen, with the dispatcher of Geilenkirchen as our neighbouring dispatcher.
Field A9293 is used offer traffic on the contra track towards Geilenkirchen. Field A9003 is used for offering trains from Geilenkirchen on contra track .
[[File:KHEZ_Geilenkirchen.png|none|Geilenkirchen|760px]]

On the right side we have the line into the direction of Aachen West. The next controlled area there is Überleitstelle (Üst) Richterich, being controlled by our neighbouring dispatcher of Aachen West. Both track there have the possibility for GWB (running on contra track/left hand running). Offering trains towards Üst Richterich is done using field A151. Field A171 is used to offer trains coming from Üst Richterich on contra track.
[[File:KHEZ_Richterich.png|none|Richterich|760px]]

=== Stations and Sidings===

==== Station of Kohlscheid ====
Der Bahnhof Kohlscheid wird von Herzogenrath aus Ferngesteuert. Hier steht vor Ort ein Dr S600 Stellwerk.
In der Regel läuft der Bahnhof Kohlscheid alleine im Selbststellbetrieb. Regionalzüge halten hier gelegentlich, in der Regel solche mit der Relation Aachen - Eschweiler St.Jöris oder nach Landgraaf. Alle anderen Züge fahren hier durch.
Aufpassen solltest du hierbei wenn du von Kohlscheid aus ins Gegengleis Richtung Aachen West fahren möchtest. Da dir eine Weichenverbindung fehlt musst du du bereits ab Herzogenrath im Gegengleis fahren.
[[File:KHEZ_Kohlscheid.png|none|Kohlscheid|760px]]

===== Overview of endbuttons Kohlscheid =====
 
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''(Start)/Target''' || '''Description'''
|-
| Kohlscheid - Herzogenrath normal track || 172II
|-
| Kohlscheid - Herzogenrath contra track || 152I
|-
| Kohlscheid - Üst Richterich normal track|| 171I
|-
| Kohlscheid - Üst Richterich contra track || 151I
|}
 

==== Station of Herzogenrath ====
The signals Asig A805 and F860, and the Asig N1 and P2 are equipped with auto-fleeting. However, this is not very useful as this will only set routes through the station via the main tracks and therefor you will have to intervene regularly. There are 4 platforms tracks in total, namelijk track 55, 1, 2 and 3. Track 55 is used for ending DMUs only, as that track is not electrified. Track 1, 2 and 3 can be used for regional trains having their stop here. You have to be aware that trains from Eschweiler St. Jöris can only be routed towards track 1 or 3, since switch 095 is just a crossing.

===== Overview of route end buttons Herzogenrath =====
 
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Description''' || '''Endbutton'''
|-
| towards Eschweiler St. Jöris || F,yyy.890II
|-
| towards Geilenkirchen normal track || 880II
|-
| towards Geilenkirchen contra track || 860II
|-
| towards Landgraaf || F,yyy.890II
|-
| Herzogenrath - Kohlscheid normal track|| 850
|-
| Herzogenrath - Kohlscheid contra track|| 803
|}
 

===== Overview of endbuttons Herzogenrath =====
 
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''(Start)/Target''' || '''Description'''
|-
| .N1 || straight D-Weg with Vmax
|-
| .N1R || D-Weg to the right with Vmax 60
|-
| .P2 || long D-Weg with Vmax
|-
| .P2K || short D-Weg with Vmax 60 up to W4
|-
| .P3 || long D-Weg on the mainline
|-
| .P3K || short D-Weg up to W6
|}
 

=== Peculiarities ===
==== Train Announcement indicator (Anrückmelder)====
A so-called "Anrückmelder" (Train Announcement indicator) has been installed due to the long distance between Eschweiler St. Jöris and our entry signal G890. This indicator starts to flash red when the train approaches the Esig G890. This is the sign for you to set the entry route into the station.
[[File:KHEZ_Anrueckmelder_aktiv.png|none|Anrueckmelder|760px]]
The indicator will stop flashing, as soon as you have set the entry route.
[[File:KHEZ_Anrueckmelder_aus.png|none|Anrueckmelder|760px]]

===="Buttons Locked"-indicator (Tastensperrmelder)====
The so-called "[[Locked Buttons Indicator|Tastensperrmelder]]" ("Buttons Locked"-indicator) indicates the following:

* dark (off) : when a route is set using the button on the panel.
* red : a route is being set using the DET or the auto-fleeting of a signal is currently setting a route.
* red blinking : the dispatcher has executed a command, which cannot be executed by the interlocking system (i.e. throwing a switch using the WGT, whilst the switch is (manually) locked)

You will find these indicator for the stations of Kohlscheid and Herzogenrath.

[[File:KHEZ_Tastensperrmelder.png|none|Tastensperrmelder|242px]]

==== Additional counters ====

In addition to the available auxiliary log printer, there are also two common counters for counting operations which are subject to logging. These counters also work in case the auxiliary log fails:

*Weichengesamtzählwerk - WGZ: counts all operations requiring logging related to switches.
[[File:KHEZ_WGZ.PNG|none|Weichengesamtzählwerk|241px]]

*Signal- und Fahrstraßengesamtzählwerk - SFGZ: counts all operations requiring logging related to signals and routes.
[[File:KHEZ_SFGZ.PNG|none|Signal- und Fahrstraßengesamtzählwerk|242px]]

==== Additional indicators - signal box Kohlscheid ====

Since signal box Kohlscheid is a remotely controlled signal box, some additional indicators are built into the panel providing information about the condition of signals and switches of the remotely controlled signal box.

*Indicator'''S''' (Signalstörmelder) : indicates that a signal has been extinguished in the area of signal box Kohlscheid.
*Indicator'''SFL''' (Signalfehlermelder) : indicates that a signal in the area of signal box Kohlscheid has a defect in a main filament of a lamp.
*Indicator'''W''' (Weichenstörmelder) : indicates a malfunction malfunction of a switch in the area of signal box Kohlscheid.
*Indicator'''Ers''' (Ersatzsignalkontrollmelder) : indicates that none of the signals in the area of signal box Kohlscheid is showing the signal aspect Zs1 or Zs7. The indicator will be lit then. The indicator will be flashing as long as a signal over there is showing aspect Zs1 or Zs7.

[[File:KHEZ_Ers.PNG|none|Ersatzsignalkontrollmelder|242px]]

==== Remote control status indicators ====

Since the set routes are not fully displayed in the station Kohlscheid, there are some remote control status indicators for the signal box of Kohlscheid. These indicators give an optical feedback to the dispatcher about whether setting a route is being executed or not. The indicators have the following meaning:

* [[Remote Control Indicators|FGrM]] lit: there is no change in the area of responsibility of signal box Kohlscheid.
* [[Remote Control Indicators|FMB]] lit: a change is taking place in the area of responsibility of signal box Kohlscheid. For example, a route is being set or track section is getting occupied or unoccupied.

Note: Only one of the indicators "FBM" and "FGrM" will be lit at the same time when something is changing in the area of Kohlscheid. So they will be blinking in turn.
[[File:KHEZ FGRM.png|none|Fernsteuerbetriebsmelder|242px]]

==Overview Offering Trains Using DET==

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsKHEZ|EN}}

==Abbreviations==

{{ShortNames:TableDetailsKHEZ|EN}}

== Track lengths ==

{{TrackLengths:TableDetailsKHEZ|EN|Herzogenrath}}
{{TrackLengths:TableDetailsKKOS|EN|Kohlscheid}}

{{Autofleet:TableDetailsKHEZ|EN}}

{{EnglishNavBottom}}

Dispatching in Stellwerk Herzogenrath

2017-03-20T00:52:50Z

Charlie:

{{EnglishNav}}

{{Sprachen_DE|DE=Örtliche Kenntnisse für Stellwerk Herzogenrath|EN=Dispatching in Stellwerk Herzogenrath|NL=Plaatselijke bekendheid in Stellwerk Herzogenrath}}

Before you get your approval to run the service on a signal box, you need to find out about the local characteristics. After training as a general trainee signalman, dispatchers were always paired with a person skilled in the signal box. This chapter is the brief introduction to the area. Read it carefully. It contains very important information.

The text is "peer to peer" written as if you are in the signal box, the first day after training.

Have a more detailed look at the [http://www.signalsimulation.com/zoom/herzogenrath/ Sp Dr S 60-Stellwerk Herzogenrath panel] here.

== Stellwerk Herzogenrath==

===Lines===
Our signalbox is located along the following 3 lines:
*2543 Herzogenrath Grenze (border) - Herzogenrath
*2550 Aachen - Kassel
*2570 Stolberg - Herzogenrath (Ringbahn)

===Neighbouring Dispatching Areas===
====Line Landgraaf - Herzogenrath (yellow line)====
The line from Herzogenrath towards Landgraaf is a cross-border route towards the Netherlands. The station there are Landgraaf and Heerlen. It is a non-electrified line and is regularly serviced by diesel multiple unita (DMU) of the series BR 642. Our neighbouring dispatcher here is the dispatcher in Landgraaf.
All trains need to offered to the neighbour prior to sending it out.

[[File:KHEZ_Landgraaf.png|none|Landgraaf|760px]]

====Line Stolberg - Herzogenrath (brown line)====
The line from Stolberg to Herzogenrath is a part of the circle line around Aachen. It currently ends in Eschweiler St.Jöris, which is also the end point for services on of this route. It is a non-electrified line and is regularly service by BR ^42 DMU's. Our neighbour here is the dispatcher of Stolberg.
Offering trains is omitted here, as one train at the time may be on this line.
[[File:KHEZ_Eschweiler.png|none|Eschweiler|660px]]

====Line Aachen - Kassel (green line)====
The electronic signal box (ESTW) Geilenkirchen took over de control of the section between Herzogenrath and Rheydt. At that same moment, the station of Übach-Palenberg was changed into a simple halt, where trains from both directions could have their stop.
We can see this on the left side of the panel (tracks 9001 and 9004).
On the left side, the line connects us with the station of Geilkirchen, with the dispatcher of Geilenkirchen as our neighbouring dispatcher.
Field A9293 is used offer traffic on the contra track towards Geilenkirchen. Field A9003 is used for offering trains from Geilenkirchen on contra track .
[[File:KHEZ_Geilenkirchen.png|none|Geilenkirchen|760px]]

On the right side we have the line into the direction of Aachen West. The next controlled area there is Überleitstelle (Üst) Richterich, being controlled by our neighbouring dispatcher of Aachen West. Both track there have the possibility for GWB (running on contra track/left hand running). Offering trains towards Üst Richterich is done using field A151. Field A171 is used to offer trains coming from Üst Richterich on contra track.
[[File:KHEZ_Richterich.png|none|Richterich|760px]]

=== Stations and Sidings===

==== Station of Kohlscheid ====
Der Bahnhof Kohlscheid wird von Herzogenrath aus Ferngesteuert. Hier steht vor Ort ein Dr S600 Stellwerk.
In der Regel läuft der Bahnhof Kohlscheid alleine im Selbststellbetrieb. Regionalzüge halten hier gelegentlich, in der Regel solche mit der Relation Aachen - Eschweiler St.Jöris oder nach Landgraaf. Alle anderen Züge fahren hier durch.
Aufpassen solltest du hierbei wenn du von Kohlscheid aus ins Gegengleis Richtung Aachen West fahren möchtest. Da dir eine Weichenverbindung fehlt musst du du bereits ab Herzogenrath im Gegengleis fahren.
[[File:KHEZ_Kohlscheid.png|none|Kohlscheid|760px]]

===== Overview of endbuttons Kohlscheid =====
 
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''(Start)/Target''' || '''Description'''
|-
| Kohlscheid - Herzogenrath normal track || 172II
|-
| Kohlscheid - Herzogenrath contra track || 152I
|-
| Kohlscheid - Üst Richterich normal track|| 171I
|-
| Kohlscheid - Üst Richterich contra track || 151I
|}
 

==== Station of Herzogenrath ====
The signals Asig A805 and F860, and the Asig N1 and P2 are equipped with auto-fleeting. However, this is not very useful as this will only set routes through the station via the main tracks and therefor you will have to intervene regularly. There are 4 platforms tracks in total, namelijk track 55, 1, 2 and 3. Track 55 is used for ending DMUs only, as that track is not electrified. Track 1, 2 and 3 can be used for regional trains having their stop here. You have to be aware that trains from Eschweiler St. Jöris can only be routed towards track 1 or 3, since switch 095 is just a crossing.

===== Overview of route end buttons Herzogenrath =====
 
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''Description''' || '''Endbutton'''
|-
| towards Eschweiler St. Jöris || F,yyy.890II
|-
| towards Geilenkirchen normal track || 880II
|-
| towards Geilenkirchen contra track || 860II
|-
| towards Landgraaf || F,yyy.890II
|-
| Herzogenrath - Kohlscheid normal track|| 850
|-
| Herzogenrath - Kohlscheid contra track|| 803
|}
 

===== Overview of endbuttons Herzogenrath =====
 
{| cellpadding="10" cellspacing="0" border="1"
|-
| '''(Start)/Target''' || '''Description'''
|-
| .N1 || straight D-Weg with Vmax
|-
| .N1R || D-Weg to the right with Vmax 60
|-
| .P2 || long D-Weg with Vmax
|-
| .P2K || short D-Weg with Vmax 60 up to W4
|-
| .P3 || long D-Weg on the mainline
|-
| .P3K || short D-Weg up to W6
|}
 

=== Peculiarities ===
==== Train Announcement indicator (Anrückmelder)====
A so-called "Anrückmelder" (Train Announcement indicator) has been installed due to the long distance between Eschweiler St. Jöris and our entry signal G890. This indicator starts to flash red when the train approaches the Esig G890. This is the sign for you to set the entry route into the station.
[[File:KHEZ_Anrueckmelder_aktiv.png|none|Anrueckmelder|760px]]
The indicator will stop flashing, as soon as you have set the entry route.
[[File:KHEZ_Anrueckmelder_aus.png|none|Anrueckmelder|760px]]

===="Buttons Locked"-indicator (Tastensperrmelder)====
The so-called "[[Locked Buttons Indicator|Tastensperrmelder]]" ("Buttons Locked"-indicator) indicates the following:

* dark (off) : when a route is set using the button on the panel.
* red : a route is being set using the DET or the auto-fleeting of a signal is currently setting a route.
* red blinking : the dispatcher has executed a command, which cannot be executed by the interlocking system (i.e. throwing a switch using the WGT, whilst the switch is (manually) locked)

You will find these indicator for the stations of Kohlscheid and Herzogenrath.

[[File:KHEZ_Tastensperrmelder.png|none|Tastensperrmelder|242px]]

==== Additional counters ====

In addition to the available auxiliary log printer, there are also two common counters for counting operations which are subject to logging. These counters also work in case the auxiliary log fails:

*Weichengesamtzählwerk - WGZ: counts all operations requiring logging related to switches.
[[File:KHEZ_WGZ.PNG|none|Weichengesamtzählwerk|241px]]

*Signal- und Fahrstraßengesamtzählwerk - SFGZ: counts all operations requiring logging related to signals and routes.
[[File:KHEZ_SFGZ.PNG|none|Signal- und Fahrstraßengesamtzählwerk|242px]]

==== Additional indicators - signal box Kohlscheid ====

Since signal box Kohlscheid is a remotely controlled signal box, some additional indicators are built into the panel providing information about the condition of signals and switches of the remotely controlled signal box.

*Indicator'''S''' (Signalstörmelder) : indicates that a signal has been extinguished in the area of signal box Kohlscheid.
*Indicator'''SFL''' (Signalfehlermelder) : indicates that a signal in the area of signal box Kohlscheid has a defect in a main filament of a lamp.
*Indicator'''W''' (Weichenstörmelder) : indicates a malfunction malfunction of a switch in the area of signal box Kohlscheid.
*Indicator'''Ers''' (Ersatzsignalkontrollmelder) : indicates that none of the signals in the area of signal box Kohlscheid is showing the signal aspect Zs1 or Zs7. The indicator will be lit then. The indicator will be flashing as long as a signal over there is showing aspect Zs1 or Zs7.

[[File:KHEZ_Ers.PNG|none|Ersatzsignalkontrollmelder|242px]]

==== Remote control status indicators ====

Since the set routes are not fully displayed in the station Kohlscheid, there are some remote control status indicators for the signal box of Kohlscheid. These indicators give an optical feedback to the dispatcher about whether setting a route is being executed or not. The indicators have the following meaning:

* [[Remote Control Indicators|FGrM]] lit: there is no change in the area of responsibility of signal box Kohlscheid.
* [[Remote Control Indicators|FMB]] lit: a change is taking place in the area of responsibility of signal box Kohlscheid. For example, a route is being set or track section is getting occupied or unoccupied.

Note: Only one of the indicators "FBM" and "FGrM" will be lit at the same time when something is changing in the area of Kohlscheid. So they will be blinking in turn.
[[File:KHEZ FGRM.png|none|Fernsteuerbetriebsmelder|242px]]

==Overview Offering Trains Using DET==

More information : [[Control Monitor Sp Dr S 600|Control Monitor Sp Dr S 600]]

{{OfferingTrainsDET:TableDetailsKHEZ|EN}}

==Abbreviations==

{{ShortNames:TableDetailsKHEZ|EN}}

== Track lengths ==

{{TrackLengths:TableDetailsKHEZ|EN|Herzogenrath}}
{{TrackLengths:TableDetailsKKOS|EN|Kohlscheid}}

{{Autofleet:TableDetailsKHEZ|EN}}

{{EnglishNavBottom}}

SimSchedule

2017-03-07T20:36:53Z

Charlie: /* Physics */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

This data is the same as what was defined in the [[TrainTypes]] table. It provides some numbers that determine locomotive and braking properties.

== Load Classes ==

A Load Class is essentially an ID number and a text description for types or ''classes'' of freight. This is not to be confused with Load Types which are more specific.

== Load Types ==

Each Load Type belongs to a Load class. For example, types such as "kerosene", "gasoline", "benzene", etc., would all belong to a class called "flammable liquids". Whereas a Load Class defines what sort of freight a car ''can'' carry, a Load Type defines what a vehicle is ''currently'' carrying.

Load Types are pieces of text that the user can see in the sim, so they need to be localised in different languages.

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


For layouts where certain train ID patterns should trigger an automatic renumbering of panel train IDs, this screen provides a method to enter such data. For each track, a number of rules can be defined. There are several types of these rules. This system operates using [https://en.wikipedia.org/wiki/Regular_expression regular expressions].

===AddSteering===

Adds a steering number to the matched train ID pattern.

===RemoveSteering===

Following a match, removes the first digit of the train ID.

===ChangeSteering===

Following a match, replace one steering number with another.

===ChangePartofNumber===

Following a match, replace the contents of the matched group with another.

===IncrementValue===

Following a match, treat the train ID as a number and increment the number by a specified value.

== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T20:30:57Z

Charlie: /* Load Types */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

A Load Class is essentially an ID number and a text description for types or ''classes'' of freight. This is not to be confused with Load Types which are more specific.

== Load Types ==

Each Load Type belongs to a Load class. For example, types such as "kerosene", "gasoline", "benzene", etc., would all belong to a class called "flammable liquids". Whereas a Load Class defines what sort of freight a car ''can'' carry, a Load Type defines what a vehicle is ''currently'' carrying.

Load Types are pieces of text that the user can see in the sim, so they need to be localised in different languages.

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


For layouts where certain train ID patterns should trigger an automatic renumbering of panel train IDs, this screen provides a method to enter such data. For each track, a number of rules can be defined. There are several types of these rules. This system operates using [https://en.wikipedia.org/wiki/Regular_expression regular expressions].

===AddSteering===

Adds a steering number to the matched train ID pattern.

===RemoveSteering===

Following a match, removes the first digit of the train ID.

===ChangeSteering===

Following a match, replace one steering number with another.

===ChangePartofNumber===

Following a match, replace the contents of the matched group with another.

===IncrementValue===

Following a match, treat the train ID as a number and increment the number by a specified value.

== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T20:26:49Z

Charlie: /* Load Classes */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

A Load Class is essentially an ID number and a text description for types or ''classes'' of freight. This is not to be confused with Load Types which are more specific.

== Load Types ==

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


For layouts where certain train ID patterns should trigger an automatic renumbering of panel train IDs, this screen provides a method to enter such data. For each track, a number of rules can be defined. There are several types of these rules. This system operates using [https://en.wikipedia.org/wiki/Regular_expression regular expressions].

===AddSteering===

Adds a steering number to the matched train ID pattern.

===RemoveSteering===

Following a match, removes the first digit of the train ID.

===ChangeSteering===

Following a match, replace one steering number with another.

===ChangePartofNumber===

Following a match, replace the contents of the matched group with another.

===IncrementValue===

Following a match, treat the train ID as a number and increment the number by a specified value.

== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T20:23:02Z

Charlie: /* IncrementValue */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

== Load Types ==

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


For layouts where certain train ID patterns should trigger an automatic renumbering of panel train IDs, this screen provides a method to enter such data. For each track, a number of rules can be defined. There are several types of these rules. This system operates using [https://en.wikipedia.org/wiki/Regular_expression regular expressions].

===AddSteering===

Adds a steering number to the matched train ID pattern.

===RemoveSteering===

Following a match, removes the first digit of the train ID.

===ChangeSteering===

Following a match, replace one steering number with another.

===ChangePartofNumber===

Following a match, replace the contents of the matched group with another.

===IncrementValue===

Following a match, treat the train ID as a number and increment the number by a specified value.

== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T20:22:27Z

Charlie: /* ChangePartofNumber */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

== Load Types ==

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


For layouts where certain train ID patterns should trigger an automatic renumbering of panel train IDs, this screen provides a method to enter such data. For each track, a number of rules can be defined. There are several types of these rules. This system operates using [https://en.wikipedia.org/wiki/Regular_expression regular expressions].

===AddSteering===

Adds a steering number to the matched train ID pattern.

===RemoveSteering===

Following a match, removes the first digit of the train ID.

===ChangeSteering===

Following a match, replace one steering number with another.

===ChangePartofNumber===

Following a match, replace the contents of the matched group with another.

===IncrementValue===

== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T20:21:58Z

Charlie: /* ChangeSteering */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

== Load Types ==

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


For layouts where certain train ID patterns should trigger an automatic renumbering of panel train IDs, this screen provides a method to enter such data. For each track, a number of rules can be defined. There are several types of these rules. This system operates using [https://en.wikipedia.org/wiki/Regular_expression regular expressions].

===AddSteering===

Adds a steering number to the matched train ID pattern.

===RemoveSteering===

Following a match, removes the first digit of the train ID.

===ChangeSteering===

Following a match, replace one steering number with another.

===ChangePartofNumber===

===IncrementValue===

== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T20:21:39Z

Charlie: /* RemoveSteering */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

== Load Types ==

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


For layouts where certain train ID patterns should trigger an automatic renumbering of panel train IDs, this screen provides a method to enter such data. For each track, a number of rules can be defined. There are several types of these rules. This system operates using [https://en.wikipedia.org/wiki/Regular_expression regular expressions].

===AddSteering===

Adds a steering number to the matched train ID pattern.

===RemoveSteering===

Following a match, removes the first digit of the train ID.

===ChangeSteering===

===ChangePartofNumber===

===IncrementValue===

== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T20:21:16Z

Charlie: /* AddSteering */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

== Load Types ==

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


For layouts where certain train ID patterns should trigger an automatic renumbering of panel train IDs, this screen provides a method to enter such data. For each track, a number of rules can be defined. There are several types of these rules. This system operates using [https://en.wikipedia.org/wiki/Regular_expression regular expressions].

===AddSteering===

Adds a steering number to the matched train ID pattern.

===RemoveSteering===

===ChangeSteering===

===ChangePartofNumber===

===IncrementValue===

== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T20:19:28Z

Charlie: /* Auto Steering */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

== Load Types ==

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


For layouts where certain train ID patterns should trigger an automatic renumbering of panel train IDs, this screen provides a method to enter such data. For each track, a number of rules can be defined. There are several types of these rules. This system operates using [https://en.wikipedia.org/wiki/Regular_expression regular expressions].

===AddSteering===

===RemoveSteering===

===ChangeSteering===

===ChangePartofNumber===

===IncrementValue===

== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T20:19:08Z

Charlie: /* Auto Steering */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

== Load Types ==

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


For layouts where certain train ID patterns should trigger an automatic renumbering of panel train IDs, this screen provides a method to enter such data. For each track, a number of rules can be defined. There are several types of these rules. This system operates using [[https://en.wikipedia.org/wiki/Regular_expression|regular expressions]].

===AddSteering===

===RemoveSteering===

===ChangeSteering===

===ChangePartofNumber===

===IncrementValue===

== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T20:18:50Z

Charlie: /* Auto Steering */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

== Load Types ==

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


For layouts where certain train ID patterns should trigger an automatic renumbering of panel train IDs, this screen provides a method to enter such data. For each track, a number of rules can be defined. There are several types of these rules. This system operates using [[regular expressions|https://en.wikipedia.org/wiki/Regular_expression]].

===AddSteering===

===RemoveSteering===

===ChangeSteering===

===ChangePartofNumber===

===IncrementValue===

== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T20:01:57Z

Charlie: /* Auto Steering */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

== Load Types ==

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


For layouts where certain train ID patterns should trigger an automatic renumbering of panel train IDs, this screen provides a method to enter such data. For each track, a number of rules can be defined. There are several types of these rules:

===AddSteering===

===RemoveSteering===

===ChangeSteering===

===ChangePartofNumber===

===IncrementValue===

== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T19:59:18Z

Charlie: /* Auto Steering */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

== Load Types ==

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are edited in the layout editor, and are separate from this option.


== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.

SimSchedule

2017-03-07T19:59:02Z

Charlie: /* Auto Steering */

SimSchedule is the proprietary tool used for editing timetables in a format that makes improvements on the older MS Access (<tt>.mdb</tt>) method of creating and editing timetables.

== Structure ==

Timetables created using SimSchedule are saved with the extension <tt>.timetable</tt> extension, but internally, the data is a file structure enclosed in a Zip file. You can take any <tt>.timetable</tt> and rename the extension to <tt>.zip</tt> and work with it the way you would with any <tt>.zip</tt> file.

The benefits of having timetable data files inside a zip file (as opposed to tables in an MS Access database) are:

* the data, in its raw form, is human-readable and human-editable
* database developers are not limited to using a single program for editing (theoretically, someone could make a tool to edit the data better than SimSchedule does)
* backwards compatibility (the ability to add new features without breaking old ones)
* data transparency (there are no mysteries in how the data is stored and edited)

== Trains ==

== Stabled Trains ==

== Soft Orders ==

== Expert Levels ==

== Paths ==

== Activity Codes ==

== Vehicles ==

== Consist Templates ==

== Physics ==

== Load Classes ==

== Load Types ==

== Special Dates ==

This data supercedes the MDB Timetable table [[SpecialDates]].

Special dates like Christmas, New Year's, and country or region-specific holidays (like Queen's Day in the Netherlands) can be defined here. Dates are defined using both day, month, and year, as some holidays occur on different dates in different years. If the timetable designer wants to have a holiday defined for a 5 year period, then 5 entries need to be made for that specific holiday.

The result of a train running on a special date is that the schedule is the same as it would be for the day of the week that's specified. If you define Christmas to be like a Sunday, then trains running on Christmas will run as though it were a Sunday, even if Christmas falls on weekday.

This screen allows for the names of special dates to be localised.

== Period Templates ==

Period templates are useful when creating many trains with commonly-used periods in which they run or do not run.

== Auto Steering ==


This feature is for defining train ID-based automatic train ID renumbering '''only'''. There are other steering systems that are editing in the layout editor, and are separate from this option.


== Translations ==

In order to localise remarks/train instructions in trains, you have the option to construct those pieces of text using short codes that are replaced with localised strings upon loading each train.

== Sanity Checks ==

Some data errors can be detected algorithmically but they are expensive (time-wise) to discover, so these checks are not performed automatically when saving or loading.

===StabledTrainCollisions===

This sanity check checks whether there are any stabled trains that will appear on the same track at the same time. Considering that every stabled train is compared with every other stabled train, on every day that it runs, this sanity check can take a considerable amount of time for timetables with many stabled trains (perhaps a minute or more).

If a problem is discovered, you will see a message similar to

<tt>Stabled trains XXXX and YYYY are on the same track(s) at the same time.</tt>

===MissingTrainData===

This checks for trains that do not have certain values specified:

* TrainModel
* Trains that are not running ''any'' days
* Trains that are not running ''any'' time periods

===MissingReferences===

This checks that missing references do not exist. For example, a train could have a consist template that does not exist. Otherwise, you will get an error message similar to:

<tt>Train XXXX missing references consist template YYYY which doesn't exist.</tt>

===PlatformStopStationNames===

This checks that the platform names for each train matches with those names defined in the layout data. Such a problem can arise when a timetable is made ''after'' changes are made to the platform names.

== Regions ==

SimSchedule supports the concept of regions, where some trains operate one one region but not others. At the moment, there is only one region to which all trains belong.

== Info ==

Provides some meta data about the timetable, including when it was first created, most recently edited, and the number of times it has been saved.

'''Creator''': Tnformation about where the timetable came from. If it was exported from an old MS Access file, it will indicate this here.

'''Created''': Date that the timetable was first created or exported.

'''Last Edited''': Date that the timetable was more recently changed using SimSchedule. Obviously, manual edits to the .timetable file will not be reflected here.

'''Revision''': Each time a timetable is saved, this version number increases by one. This provides an automatic version control scheme.

===Optimisations===

SimSchedule has a few options in how data is stored internally. Originally, the system was designed so that one train was saved per file, within the .timetable archive. Since each .timetable file is just a zip file, this method of saving creates a ''lot'' of small files. It is faster and more efficient to write fewer, larger files than many smaller ones. Switching these options on can drastically reduce the size of timetable files, at the expense of some human-readability. If you are not intending to ever unzip a .timetable file and edit manually, these options should be checked/on.