Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 2 railML 2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.orgrailML.org
  • railML 2railML 2
  • Issues
  • #227
Closed
Open
Issue created Mar 11, 2013 by Deleted User@deleted-user

Mandatory braking in front of a steep gradient (de: Betriebsbremung)

Description

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.

Links

  • Forum discussion:
  • Susanne Wunsch, March 2013: [https://www.railml.org/forum/index.php?t=msg&th=143&goto=517&#msg_517]
  • Trac ticket:
  • Wiki documentation:
  • SpeedChange: [http://wiki.railml.org/index.php?title=IS:speedChange]

Proposed solution in railML 2.4

There is no need for a specific new attribute or element within . Interested users should for the beginning use an own extension in and come up with a proposal for railML 3.x implementation if required.

For clarification, the result of the discussion about mandatory braking points has been added as note on the railML wiki page about of the .

Assignee
Assign to
Time tracking

railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany