Search results
Jump to navigation
Jump to search
- tools use their own internal generic interlocking (table) model. Thus this use case does not require a interlocking table. This distinguishes this IL UC from7 KB (959 words) - 14:06, 7 December 2023
- exchange format. This use case concerns the exchange of engineering data for tailoring an interlocking to fit a station. This use case focuses on "legacy"11 KB (828 words) - 13:25, 13 March 2023
- cable plan Subschema: Interlocking For general information on use cases see UC:Use cases1 KB (119 words) - 13:51, 13 March 2023
- interlockings has to be incorporated into the operation and control systems. They uses the interlocking to operate elements get element status schedule and manage2 KB (209 words) - 13:52, 13 March 2023
- UC:IL:EulynxDataPreparationInterlocking (category Use case (IL))reflect the as-built situation. Please refer to the linked use cases that cover the Eulynx use case. For detailed information please refer to the website https://eulynx3 KB (450 words) - 17:54, 27 June 2022
- UC:IL:SitePreparationDataForSignalControlledWarningSystems (category Use case (IL)) (section Use case / Anwendungsfall)enters a warning area) ETCS ID of the SCWS Timeout for simplified search in case of a switch fault Signaling type of this SCWS (stationary, ETCS Level 1,4 KB (571 words) - 13:51, 13 March 2023
- UC:IL:InterlockEngineeringForSignallingWithinJBV (category Use case (IL)) (section Use case / Anwendungsfall)together especially when gathering information regarding topology. Future use case should handle integration towards 3D modelling for evaluation of e.g. sight5 KB (558 words) - 13:53, 13 March 2023
- Current UML visualization A list of use cases for railML's interlocking scheme can be found here Category:Use_case_(IL). Interlocking Concepts — explanations1 KB (153 words) - 18:26, 3 November 2023
- UC:Use cases (section What is a use case?)– IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases View/edit list on the separate source page If you want to reactivate your inactive use case7 KB (287 words) - 15:43, 8 April 2024
- Main Page (section Interlocking (IL))RailTopoModel (external link). A list of use cases for the railML® interlocking schema can be found on page Category:Use case (IL). →Main Article: Infrastructure10 KB (1,041 words) - 10:56, 2 May 2024
- IL:switchIL (category Missing Attribute Documentation/IL)n> </derailerIL> </derailersIL> Dependent on the language variant there are several terms in use: point, turnout, switch. railML will use the term „switch“19 KB (1,714 words) - 09:32, 3 May 2023
- IL:derailerIL (category Missing Attribute Documentation/IL)This marks the position, which the derailer shall have in normal case, i.e. when not in use of a route. The possible positions can be derailingPosition –5 KB (484 words) - 12:44, 27 May 2022
- IL:movableCrossing (category Missing Attribute Documentation/IL)position. In case of switch actuators connected to the crossing for changing its position the attribute @numberOfFrogSwitchActuators shall be used to identify15 KB (1,510 words) - 19:13, 14 February 2022
- station, train number field, timetable element) to the next. For example, one use case is a TMS that provides the current (dispatching) timetable and train positions16 KB (1,407 words) - 11:50, 18 July 2022
- IL:tvdSection (category Pages using Tabber parser tag)<hasExitSignal> – This is the reference to a <signalIL> which protects the exit from this TVD section. It shall be used in case @isBerthingTrack is set to true. Within7 KB (829 words) - 15:11, 27 May 2022
- IL:interlocking (category Pages using Tabber parser tag)common module (common3.xsd) are used. In addition two basic types were created for use in interlocking subschema – entityIL and entityILref. They give the4 KB (493 words) - 10:38, 31 May 2021
- IL:route (category Pages using Tabber parser tag)route lock is only applied when a train is approaching the route. In that case this time is the minimum required before the final route lock can be applied9 KB (1,077 words) - 08:15, 7 May 2022
- IL:levelCrossingIL (category Pages using Tabber parser tag)even not all information may be really “known” to the interlocking, i.e. in case of autonomous level crossing. @elementNumber - A positive integer number18 KB (1,997 words) - 15:11, 4 June 2022
- IL:keyLockIL (category Pages using Tabber parser tag)released for removal. The key is a simple mean of authorisation transfer as its use allows the manual operation of a moveable element. The lock with control from4 KB (531 words) - 19:18, 29 January 2020
- Infrastructure Related subschemas: IL TT RS Reported by: ProRail For general information on use cases see UC:Use cases3 KB (343 words) - 13:44, 13 March 2023
- IL:key (category Pages using Tabber parser tag)The Boolean value gives indication whether the key is of physical type for use in a mechanical lock.964 bytes (88 words) - 19:16, 29 January 2020
- IL:signalIL (category Pages using Tabber parser tag)which is neither used as block, entry, exit nor intermediate signal. This is the more general function in case no specific one can be used. repeater – The9 KB (1,314 words) - 10:15, 19 May 2023
- than in use case ETCS-a because data such as balises or routes will be added. The amount of the data to be exchanged is the same as in use case ETCS-a.5 KB (441 words) - 09:30, 12 June 2023
- IL:signalIndicator (category Pages using Tabber parser tag)unique identifier used to reference this element within railML. @indicatorType - There is currently only cautiousDriving defined for use. Other values might2 KB (240 words) - 13:40, 28 May 2022
- IL:permissionZone (category Pages using Tabber parser tag)the set of assets for which the permission is transferred. In the simple case the permission can only be changed for the entire station or interlocking1 KB (151 words) - 19:42, 29 January 2020
- signalling; CAD für Zugsignalisierung Engineers of the railway signaling discipline use a Computer-Aided Design (CAD) tool to model a railway construction project1 KB (127 words) - 14:12, 7 December 2023
- Subschema: Rollingstock Related subschemas: IS IL TT For general information on use cases see UC:Use cases1 KB (146 words) - 13:29, 13 March 2023
- IL:genericDetector (category Pages using Tabber parser tag)interlocking needs to trigger the self-test of the detector. It has to be used in combination with @triggeredSelfTest. <detectorType> – This is the reference2 KB (218 words) - 19:17, 29 January 2020
- Schematic Track Plan Infrastructure managers use maps for the visualization of their railway infrastructure. These maps comprise: Geographic maps Geoschematic4 KB (198 words) - 16:57, 13 February 2023
- the infrastructure and state their validity. The infrastructure used in this use case is not based on the current infrastructure but an agreed future infrastructure4 KB (523 words) - 11:14, 18 July 2022
- IL:trainNumberField (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further3 KB (348 words) - 13:08, 28 May 2022
- UC:IS:CaptureSchematicVisualisationInformationOfTrackAssets (category Use case (IS)) (section Use case / Anwendungsfall)von Schienenanlagen railML data will be used for engineering signalling and interlocking systems. Engineers are used to working with paper plans that schematically3 KB (383 words) - 13:44, 13 March 2023
- IL:movableBridge (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further3 KB (405 words) - 15:00, 27 May 2022
- IL:implementsSignalplan (category Pages using Tabber parser tag)signal is showing. This element shall be used for “old-style” signalling systems with separate distant signals or in case of repeaters within the route. <signalsSpeedProfile>17 KB (1,655 words) - 17:19, 30 January 2020
- master data for the use case "passenger information inside the train". The information from the <timetable> are data which will be used individually for every9 KB (677 words) - 18:10, 27 June 2022
- control. This use case aims to cover all data exchange necessary for the functions listed above. A major difference to previous railML use cases is that this2 KB (179 words) - 17:27, 13 February 2023
- IL:conflictingRoute (category Pages using Tabber parser tag)value is used in case of any TVD section of the route is also used by the conflicting one. ConflictingHeadProtection – This value is used in case any signal5 KB (573 words) - 12:09, 28 May 2022
- IL:interface (category Pages using Tabber parser tag)element. @bitNr – This is the order number of the command in the list. In case of transmission as complete bitmask it defines the bit position in the byte13 KB (1,119 words) - 17:46, 30 January 2020
- UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers (category Use case (IS)) (section Use case / Anwendungsfall)Export of planning tool: planning data, handing-over to the supplier (by using a database). interlocking (see also: Interlocking Engineering) This section3 KB (367 words) - 13:47, 13 March 2023
- Infrastructure Related subschemas: IL TT RS Reported by: Jernbaneverket For general information on use cases see UC:Use cases5 KB (687 words) - 13:46, 13 March 2023
- IL:routeExit (category Pages using Tabber parser tag)is the reference to the physical end of the route path. This is in most cases a signal but can also be a buffer stop or just a train detection device when2 KB (187 words) - 20:37, 29 January 2020
- IL:assetsForIL (category Pages using Tabber parser tag)infrastructure subschema. In such cases just the suffix “IL” was added to the name, e.g. signalIS vs. signalIL. The element of <assetsForIL> is not only a collection2 KB (272 words) - 12:02, 21 May 2022
- IL:switchIL/3.2 (category Missing Attribute Documentation/IL)Automatic Schemaexport for Element switchIL5 KB (5 words) - 12:41, 8 February 2024
- IL:assetsForInterlocking (category Pages using Tabber parser tag)in infrastructure subschema. In such cases just the suffix “IL” was added to the name, e.g. signalIS vs. signalIL. The element of <assetsForInterlocking>3 KB (359 words) - 13:19, 29 May 2022
- Automatic Schemaexport for Element switchIL4 KB (5 words) - 14:21, 24 January 2020
- IL:reasonForConflict (category Pages using Tabber parser tag)conflictingOverlap: This value is set in case of the overlap of either route causes the conflict. conflictingStatus: This value is used in case the status of any element520 bytes (9 words) - 18:50, 19 December 2019
- IL:hasTVDresetStrategy (category Pages using Tabber parser tag)They deliver mainly the status information vacant, occupied or failed. In case of a failure the particular sections needs to be reset, i.e. declared clear4 KB (406 words) - 17:47, 22 January 2020
- IL:tunnelGateIL (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further5 KB (599 words) - 14:26, 27 May 2022
- IL:activationCondition (category Pages using Tabber parser tag)conditions to conclude a train is approaching the level crossing. In first case this happens when the train crosses a detection point, i.e. an insulated4 KB (465 words) - 12:14, 30 May 2020
- IL:relatedMovableElement (category Pages using Tabber parser tag)for element IL:relatedMovableElement of railML® version 3.2 UML-visualization of IL Documentation reference to other movable element in case of single/double524 bytes (5 words) - 18:47, 19 December 2019
- Automatic Schemaexport for Element derailerIL4 KB (5 words) - 14:21, 24 January 2020
- not in use. (optional; xs:string) Possible values: upleft-rightdown downleft-rightup, maxThrowTime: Maximum time in milliseconds during which the IL can drive4 KB (5 words) - 14:21, 24 January 2020
- IL:routeEntry (category Pages using Tabber parser tag)<refersTo> – This is the reference to the start element of the route. In most cases this is a signal. Preferable the reference shall be made to the element with1 KB (151 words) - 20:08, 29 January 2020
- IL:routeSequence (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further516 bytes (38 words) - 21:53, 25 April 2022
- IL:derailerIL/3.2 (category Missing Attribute Documentation/IL)Automatic Schemaexport for Element derailerIL5 KB (5 words) - 12:41, 8 February 2024
- IL:movableCrossing/3.2 (category Missing Attribute Documentation/IL)throwing adds a delay to route setting that is of great interest to the use case simulation. For this purpose, we add an attribute typicalThrowTime that allows5 KB (5 words) - 12:41, 8 February 2024
- IL:dangerPoint (category Pages using Tabber parser tag)point is located. It is used when the danger point is situated in the middle of a TVD section or beyond any TVD section in case of not supervised tracks2 KB (232 words) - 20:39, 29 January 2020
- IL:combinedRoute (category Pages using Tabber parser tag)element in internal lists of engineering data. @id - The unique identifier used to reference this element within railML. @priorityRank – The positive integer3 KB (348 words) - 12:05, 28 May 2022
- IL:hasLevelCrossingType (category Pages using Tabber parser tag)deactivated only from interlocking independently of the direction. This is the case for level crossings within stations. The level crossing is activated by route3 KB (405 words) - 15:31, 29 October 2023
- Autoexport from the XML-Schema for element IL:tvdSection of railML® version 3.1 UML-visualization of IL Documentation track vacancy detection (TVD) section2 KB (5 words) - 14:21, 24 January 2020
- IL:situatedAtTrackAsset (category Pages using Tabber parser tag)Autoexport from the XML-Schema for element IL:situatedAtTrackAsset of railML® version 3.2 UML-visualization of IL Documentation This is the reference to the523 bytes (5 words) - 18:51, 19 December 2019
- The railML® wiki offers a number of Use Cases. A Guideline to implementing Use Cases can be found under Dev:Use cases. In contrast to railML® 2, railML®12 KB (1,475 words) - 15:28, 15 April 2024
- Autoexport from the XML-Schema for element IL:tvdSection of railML® version 3.2 UML-visualization of IL Documentation track vacancy detection (TVD) section3 KB (5 words) - 12:41, 8 February 2024
- IL:initStatus (category Pages using Tabber parser tag)element IL:initStatus of railML® version 3.2 UML-visualization of IL Documentation The initial status of commands and messages on the interface in case of "cold513 bytes (0 words) - 18:48, 19 December 2019
- IL:routeStatusIndicator (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further2 KB (200 words) - 13:21, 28 May 2022
- Automatic Schemaexport for Element levelCrossingIL3 KB (5 words) - 14:21, 24 January 2020
- IL:hasAspect (category Pages using Tabber parser tag)the train using its horn or bell. Use the values warning or caution instead for aspects of distant signals or indicators. This aspect is used for announcing8 KB (1,085 words) - 10:48, 10 November 2023
- Automatic Schemaexport for Element levelCrossingIL4 KB (5 words) - 12:41, 8 February 2024
- aspectk). Other functional classes can make use of these tuples. The using of the state space is twofold: direct use of (asset, state) tuples with class assetAndState5 KB (562 words) - 11:57, 30 May 2020
- IL:hasConfiguration (category Pages using Tabber parser tag)information. The configuration example below just shows the use of the attributes without using realistic values especially for @model and @SWversion. <hasConfiguration3 KB (385 words) - 14:00, 21 August 2021
- IL:branchTip (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further512 bytes (38 words) - 21:51, 25 April 2022
- IL:refersToInfrastructureElement (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further532 bytes (38 words) - 21:53, 25 April 2022
- IL:etcsGeneralData (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further518 bytes (38 words) - 21:53, 25 April 2022
- conflictingOverlap: This value is set in case of the overlap of either route causes the conflict. conflictingStatus: This value is used in case the status of any element2 KB (5 words) - 12:42, 8 February 2024
- Automatic Schemaexport for Element signalIL7 KB (5 words) - 12:41, 8 February 2024
- Autoexport from the XML-Schema for element IL:hasTVDresetStrategy of railML® version 3.2 UML-visualization of IL Documentation Classification of TVD section2 KB (5 words) - 12:42, 8 February 2024
- system in which case this attribute should be omitted. (optional; xs:boolean), priorityRank: Gives the priority of the route path in case there are several4 KB (5 words) - 12:42, 8 February 2024
- onBeforeDangerPoint> <objectName> <situatedAtTrackAsset> <derailersIL> <derailerIL> <assetName> <belongsToOperationalPoint> <connectedToPowerSupply> <designator>188 KB (2,767 words) - 13:38, 4 December 2023
- the tip branch. Especially in case of switch crossing this element is not used. Subschema interlocking Parents* switchIL Children None Attributes: ref:844 bytes (5 words) - 21:51, 25 April 2022
- element IL:initStatus of railML® version 3.2 UML-visualization of IL Documentation The initial status of commands and messages on the interface in case of "cold846 bytes (5 words) - 16:17, 5 March 2021
- element IL:initStatus of railML® version 3.1 UML-visualization of IL Documentation The initial status of commands and messages on the interface in case of "cold846 bytes (5 words) - 18:48, 19 December 2019
- for element IL:routeExit of railML® version 3.1 UML-visualization of IL Documentation Description of the route destination point. In most cases the route1,018 bytes (5 words) - 14:22, 24 January 2020
- Autoexport from the XML-Schema for element IL:situatedAtTrackAsset of railML® version 3.2 UML-visualization of IL Documentation This is the reference to the920 bytes (5 words) - 16:18, 5 March 2021
- Autoexport from the XML-Schema for element IL:situatedAtTrackAsset of railML® version 3.1 UML-visualization of IL Documentation This is the reference to the919 bytes (5 words) - 18:19, 23 December 2019
- for element IL:relatedMovableElement of railML® version 3.2 UML-visualization of IL Documentation reference to other movable element in case of single/double890 bytes (5 words) - 16:16, 5 March 2021
- for element IL:relatedMovableElement of railML® version 3.1 UML-visualization of IL Documentation reference to other movable element in case of single/double889 bytes (5 words) - 14:21, 24 January 2020
- Autoexport from the XML-Schema for element IL:refersToInfrastructureElement of railML® version 3.2 UML-visualization of IL Documentation The reference to an element935 bytes (5 words) - 21:53, 25 April 2022
- Autoexport from the XML-Schema for element IL:combinedRoute of railML® version 3.2 UML-visualization of IL Documentation a concatenation of single routes2 KB (5 words) - 12:42, 8 February 2024
- Autoexport from the XML-Schema for element IL:routeSequence of railML® version 3.2 UML-visualization of IL Documentation RouteSequence is a combination2 KB (5 words) - 12:42, 8 February 2024
- for element IL:routeExit of railML® version 3.2 UML-visualization of IL Documentation Description of the route destination point. In most cases the route1 KB (5 words) - 12:42, 8 February 2024
- IL:radioBlockCenter (category Pages using Tabber parser tag)This element does not appear in railML® 3.2 within the IL subschema. It is available only in railML® . Do not hesitate to contact railML.org for further5 KB (671 words) - 05:46, 18 April 2022
- XML-Schema for element IL:routeStatusIndicator of railML® version 3.2 UML-visualization of IL Documentation virtual logical object used for indication of route1 KB (5 words) - 12:41, 8 February 2024
- Autoexport from the XML-Schema for element IL:route of railML® version 3.1 UML-visualization of IL Documentation path for train movements in railway network3 KB (5 words) - 14:22, 24 January 2020
- Autoexport from the XML-Schema for element IL:etcsGeneralData of railML® version 3.2 UML-visualization of IL Documentation list of main ETCS variables of2 KB (5 words) - 12:42, 8 February 2024
- IL:etcs (category Pages using Tabber parser tag)This element does not appear in railML® 3.2 within the IL subschema. It is available only in railML® . Do not hesitate to contact railML.org for further2 KB (329 words) - 08:04, 8 May 2021
- Autoexport from the XML-Schema for element IL:hasLevelCrossingType of railML® version 3.2 UML-visualization of IL Documentation Classification of basic level2 KB (5 words) - 12:42, 8 February 2024
- element IL:hasAspect of railML® version 3.2 UML-visualization of IL Documentation Classification of signal aspects. Subschema interlocking Parents* usesTypes3 KB (5 words) - 12:42, 8 February 2024
- is implemented using relations with a navigability attribute (in the The RailTopoModel® wiki). The condensed relations matrix for this case is presented18 KB (2,052 words) - 18:20, 15 April 2024
- <designator> <isLimitedBy> <signalsIL> <signalIL> <any> <designator> <protectsBlockExit> <refersTo> <switchesIL> <switchIL> <any> <branchLeft> <branchRight>125 KB (1,906 words) - 03:09, 26 October 2023
- the railML® website). Codelists are intended to address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity17 KB (299 words) - 15:10, 7 December 2023