technical stopping times for formation

on request of Jernbanedirektoratet: For timetable planning purposes we need to know the minimal technical times for the following stopActivities (I’m using values from the new railML2.4 TT:stopActivity list for common compliance; https://wiki.railml.org/index.php?title=TT:times).

The list might become longer in the future…

• join: collect motor unit – Stärken/Vereinigen Couple vehicles / train parts - intended for self-propelling train parts. Please consider relation to formations (as far as used) Vereinigen von Zugteilen – vorgesehen für selbstfahrende Zugteile. Zusammenhang zur konkreten Formation beachten (sofern verwendet)

• split: drop motor unit – Schwächen/Trennen Uncouple vehicles / train parts - intended for self-propelling train parts. Please consider relation to formations (as far as used) Trennen („Flügeln“) von Zugteilen – vorgesehen für selbstfahrende Zugteile. Zusammenhang zur konkreten Formation beachten (sofern verwendet)

• reverse: Richtungswechsel Stop to change driving direction of train. Consider relation to @formationReversed Halt zum Fahrtrichtungswechsel des Zuges. Zusammenhang beachten zu @formationReversed

As mentioned we need the technical times. Not the complete operational. So for a “reverse” the time duration would be from stand still of the train over shut down the drivers cabin for the initial train driver to the time a second train driver in the opposite drivers cabin has initiated the train and is ready for departure. Normaly the train driver would walk to the other drivers cabin, but this would be considered an operational time. As the times are technical I suggest to place the element under .

We might consider to add also other variants of the times as well like combinations of “operational” and “maximum” and “average” .

So maybe something like this:

I am a bit uncertain about the correct terms here.

Instead of using @scope=”operational” the element could be duplicated under .

For the time we can park the attributes @scope, @range @state as we only use the values scope=technical range=minimum and state=planned.