|Definition of Emergency Stop Area for railML 3.3 [message #3140]
||Sun, 15 October 2023 09:36
Registered: December 2022
for railML 3.3 we need the definition of an Emergency Stop Area.
There are two types of Emergency Stop Areas:
1. Conditional Emergency Stop Area // train has to stop if the front end of the train is in rear of the start of the ESA
2. Unconditional Emergency Stop Area //train has to stop in each case
A suggestion would be to use the same definition for Emergency Stop Area like for WorkZone or LocalOperationArea.
However, to use the same approch we must clarify in advance:
What borders are possible for an Emergency Stop Area?
Is at the border in each case a track asset defined (case 1)?
Or is it also possible that the borders are on a pure kilometer value defined without a track asset behind (case 2)?
For case 1 it would be enough to define the Emergency Stop Area only in the interlocking schema, like we did for WorkZone and LocalOperationArea.
For case 2 the definition of the Emergency Stop Area would be necessary in infrastructure (to define the extension) and interlocking schema.
Here an example for an Emergency Stop Area defined only in interlocking schema:
<emergencyStopArea id="IL_Z2MkZDPoiVaqfOJkdtaGyJFa" type="conditional">
<designator register="_costId" entry="EmergencyStopArea:BGS_ESA_BOR"/>
<designator register="_sci_cc" entry="NO_A29_BORESABOR____"/>
<designator register="_longName" entry="BGS_ESA_BOR"/>
<!--commands: NSO, NSOF-->
Therefore the question:
Which borders are possible for Emergency Stop Areas?
Data Manager TMS Norway
GTS Deutschland GmbH
Phone: +49 (0) 30 688306 423
Schützenstr. 25 10117 Berlin Germany
|Re: Definition of Emergency Stop Area for railML 3.3 [message #3167 is a reply to message #3140]
||Mon, 20 November 2023 06:37
Jörg von Lingen
Registered: March 2016
Thanks Heidrun for this post.|
The definition of borders of an ESA will come from operational rules of the infrastructure manager.
When considering only IL domain for definition of ESA one would always need some kind of track asset (signal, detection point etc.) as border elements. Otherwise it might be conceivable to define special border elements in IS which are then referred to.
As proposed such ESA can use a similar definition as for WorkZone or LocalOperationArea. However, for the modelling in railML3.3 it needs to be discussed before what is needed in addition to border elements.
1) isLimitedBy = reference to border elements
2) trackAssetInArea = references to any track assets inside (optional/mandatory)?
3) any track asset states?
4) any additional information, e.g. validity?
Dr.-Ing. Jörg von Lingen - Interlocking scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 351 87759 40; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org