20620: What is the "minimum remaining period" that can be set at general network data (ALT+V in the overview window) in the tab Techn. data?
The minimum remaining period is a relic from the steam locomotives and was meant to go easier on man and machine, at least when on time. It states that there must be a minimum period of time between an acceleration and a subsequent braking process. It is fixed to 30s in Germany and is therefore also known as "30s rule".
If there is no maintenance of speed between acceleration and braking, this is referred to as "driving sharp". It is relatively stressful (also figuratively) for the driver, but also for travellers and traction vehicles, since it assumes, at least theoretically, a direct change of forces from traction to brake. On the other hand, from today's point of view, it also seems unrealistic that a driver can calculate so far in advance, that he the withdraws the tractive force 30 seconds before a potential brake application point.
Overall, it can be determined by a few simple comparisons (e.g. with train diagrams from the graphic timetable) that a minimum holding time of approx. 30 s usually only increases travel time requirements slightly, but leads to a considerable energy saving. It is therefore recommended not to completely switch off the minimum holding time but to use a value between 5s and 30s.
For the infrastructure of DB Netz AG, a minimum holding time of 30 s is required in its directives 457 and 402 (state 12/2005 and 06/2005). However, a number of exceptions are mentioned under item 457.0201.5 (10b) point 3. In particular, within the framework of Directive 457, the minimum retention period is to avoid of unnecessary or non-sensible accumulations of speed changes. However, the “30s rule” nowadays also correlates to energy, personnel and vehicle technology, the decision of the minimum retention time is also the responsibility of the respective TOC.
Last update on 19.03.2020 by iRFP Support.