Interlocking: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [checked revision] |
No edit summary |
m (1 revision imported: http→https) |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{head|Interlocking}} | {{head|Interlocking}} | ||
The [[interlocking|interlocking subschema]] will focus on information that infrastructure managers and signal manufacturing industry typically maintain in signal plans and route locking tables: | The [[interlocking|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. | *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 {{rml}} 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. | *Simulation programs: the {{rml}} 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. | ||
The main element is [[IL:interlocking]]. | |||
A complete element list can be found under [[:Category:Interlocking Elements]] | |||
==Documentation== | ==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 | 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 {{external|https://www.railtopomodel.org|RailTopoModel}}. | ||
* A list of use cases for railML's interlocking scheme can be found here [[IL | * [{{uml|IL}} Current UML visualization] | ||
* A list of [[dev:Use Cases|use cases]] for railML's interlocking scheme can be found here [[:Category:Use_case_(IL)]]. | |||
* Interlocking Concepts — explanations of some basic modelling concepts to this subschema: | * Interlocking Concepts — explanations of some basic modelling concepts to this subschema: | ||
** [[: | <!--** [[:Category:Interlocking Concept|List of Articles describing basic interlocking concepts]]--> | ||
**[[Dev:Moveable Elements|Moveable Elements]] | **[[Dev:Moveable Elements|Moveable Elements]] | ||
Revision as of 11:32, 14 February 2021
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.
The main element is IL:interlocking.
A complete element list can be found under Category:Interlocking Elements
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 (external link).
- Current UML visualization
- A list of use cases for railML's interlocking scheme can be found here Category:Use_case_(IL).
- Interlocking Concepts — explanations of some basic modelling concepts to this subschema: