Interlocking: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
No edit summary
Line 7: Line 7:
* A list of use cases for railML's interlocking scheme can be found here [[IL:UseCases]].
* A list of use cases for railML's interlocking scheme can be found here [[IL:UseCases]].
* Interlocking Concepts — explanations of some basic modelling concepts to this subschema:
* Interlocking Concepts — explanations of some basic modelling concepts to this subschema:
** [[:<ref name="ftn2"> Dependent on the language variant there are several terms in use: common crossing, frog. railML will use the term “frog” to avoid ambiguity.</ref>|List of Articles describing basic timetable concepts]]
** [[:Category:Interlocking Concept|List of Articles describing basic timetable concepts]]
**[[Dev:Moveable Elements|Moveable Elements]]
**[[Dev:Moveable Elements|Moveable Elements]]

Revision as of 16:27, 24 January 2020

Interlocking
 
The interlocking subschema will focus on information that infrastructure managers and signal manufacturing industry typically maintain in signal plans and route locking tables:

  • Data transfer: a standard data exchange format will allow the automation of data transfer, which is the process of adapting a railway interlocking and signaling system to a specific yard.
  • Simulation programs: the railML® IL schema allows modelers to quickly absorb information about the interlocking systems such as timing behavior and routes and analyze the impact on railway capacity.

Documentation

The subschema is currently under development with the participation of some European infrastructure managers and the signal manufacturing industry based on railML 3 and UIC's RailTopoModel.