Home » railML newsgroups » railML.infrastructure » last open points for speedProfiles in railML 2.2
Re: Mandatory braking in front of a steep gradient [message #529 is a reply to message #517] Sat, 16 March 2013 13:11 Go to previous messageGo to previous message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Dear Susanne,

Am 11.03.2013 16:20, schrieb Susanne Wunsch:
> I summarized the opinions from the conference in Trac ticket #227 [2]:
>
> During the last railML conference (2013-03-06) in Berlin the
> discussion came to this aspect of the current speedChange
> implementation:
>
> If a goods train driver has not used its train brakes during a
> specified time (e.g. last hour) it should do an "operational
> braking" - not until standstill, but to check, if the brakes work
> properly.
>
> This operation is indicated at the drivers timetable.
>
> It seems, that the scenario is a very special German one, that is
> covered by the German operational rules. Brake tests are done very
> differently across other countries. It is not a general infrastructure
> specific issue, but more an operational one.
>
> Therefore the implementation of "mandatoryBraking" in the element
> "speedChange" should be removed.
>
> railML partners should use an "any"-Attribute as a short-term solution.
>
> For re-inventing this feature it should be modeled in another way.
> There were no further proposals.

+1

> [2] http://trac.assembla.com/railML/ticket/227

Regards

--
Christian Rahmig
railML.infrastructure coordinator

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Maximum train current - Proposal for extension of infrastructure scheme in railML 2.4
Next Topic: Track: description vs. trackDescr
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat May 04 20:26:16 CEST 2024