Search results
Jump to navigation
Jump to search
- 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
- UC:Use cases (section What is a use case?)(UML). Examples are solutions to use cases. CO Use Cases – IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases View/edit list on the separate source7 KB (287 words) - 16:17, 13 May 2024
- essential for the use case or considered optional. Please describe what data is exchanged for the use case. What is part and what is not part of the data exchange2 KB (263 words) - 17:26, 5 February 2024
- offline simulation for capacity management. Implicitly, train dispatching is seen as a logical prolongation of a detailed timetable. At disruptions during3 KB (343 words) - 13:44, 13 March 2023
- be assembled and visualised. For this purpose, railML infrastructure data is to be supplemented with basic information on the type, extent, and localization4 KB (354 words) - 16:37, 4 December 2023
- Dev:Use cases (section What is a use case?)for the use case or considered optional. Characterizing data Please describe what data is exchanged for the use case. What is part and what is not part7 KB (1,035 words) - 17:27, 5 February 2024
- 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
- exchanged is bigger 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 as5 KB (441 words) - 09:30, 12 June 2023
- UC:IS:RailwayInfrastructureVisualisation (category Use case (IS)) (section Use case / Anwendungsfall)Visualisation (RAIV) Subschema: Infrastructure For general information on use cases see UC:Use cases2 KB (180 words) - 13:43, 13 March 2023
- will also be responsible for RINF Reporting to the European Union. This use case describes the current structure of the yearly report of ÖBB Infrastructure2 KB (225 words) - 13:45, 13 March 2023
- other hand. It is a combination of defined organizational processes and a complete database application system. This database system is receiver and sender3 KB (117 words) - 13:45, 13 March 2023
- 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
- existing topology database is based on the track circuits. In order to enable desired functions, the creation of the data model is essential to become a basis3 KB (427 words) - 17:57, 27 June 2022
- 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
- detailed that is envisioned for this use case is a microscopic description of the timetable. The use case is divided into three sub-use cases based on the6 KB (858 words) - 12:09, 25 March 2024
- main element for this schema is <rollingstock>, which is the root for data about any rolling stock. It is intended to use this data schema for vehicle3 KB (458 words) - 17:20, 29 November 2023
- the maintenance planning system of the infrastructure manager. The data flow is one-directional: It goes from the (central) asset management source data base1 KB (133 words) - 13:47, 13 March 2023
- information system of the same (or another) infrastructure manager. The data flow is one-directional: It goes from the resource planning system to the passenger1 KB (157 words) - 13:46, 13 March 2023
- 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 (178 words) - 18:16, 13 May 2024
- access and use of the rail network (route network) of the infrastructure manager. It provides all the technical and operational information that is necessary2 KB (169 words) - 11:34, 12 April 2024
- IS:isSpeedSignal (category Pages using Tabber parser tag)according to [1] <isValid> is used to mark a start and end days. [1] https://documents.railml.org/schemas/usecase/railml-use-case_is-nest.pdf2 KB (205 words) - 15:47, 24 March 2023
- Infrastructure Reported by: Bahnkonzept For general information on use cases see UC:Use cases3 KB (335 words) - 13:48, 13 March 2023
- UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers (category Use case (IS)) (section Use case / Anwendungsfall)software), have to be given to the supplier. The content of the data exchange is the result of the planning process, so the data are provided by a specialized3 KB (367 words) - 13:47, 13 March 2023
- railML® for RINF Reporting; railML® für RINF Meldung This use case aims at providing a railML3 file, fulfilling the functional requirements published by3 KB (297 words) - 13:49, 13 March 2023
- Advisory System (DAS); Fahrerassistentsystem The Driver Advisory System (DAS) is an on-train driver support system which advises a driver on the most energy-efficient3 KB (306 words) - 13:48, 13 March 2023
- positioning system, which is a multi-sensor on-board positioning device, the train can determine its position itself. The digital map is a key component of such3 KB (367 words) - 13:49, 13 March 2023
- The objective of a possession is to ensure safe construction/maintenance works on the railway infrastructure. The safety is ensured by a set of safety measures:3 KB (394 words) - 12:02, 18 July 2022
- infrastructure is pulled from an asset management database. Future infrastructure is designed by hand from technical drawings. The timetable model is tested either5 KB (687 words) - 13:46, 13 March 2023
- The infrastructure used in this use case is not based on the current infrastructure but an agreed future infrastructure state. It is important that any4 KB (523 words) - 11:14, 18 July 2022
- verify the results of the work in very detailed manner. The track geometry use case deals with two major data flows between two major components. They are5 KB (737 words) - 16:12, 15 April 2024
- Infrastructure (section Infrastructure (IS))IS root element — IS use cases — Concepts & examples The railML® Infrastructure subschema is focused on the description of the railway network infrastructure3 KB (288 words) - 18:47, 20 March 2024
- 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
- Interlocking Rollingstock The use case comprises static and dynamic (status) asset data. For infrastructure, the focus is only on static data. Small (operational10 KB (129 words) - 16:01, 27 September 2023
- electrical simulation is not possible with the necessary accuracy without simulating the process of railway operation. Thus this use case is always an addon2 KB (236 words) - 13:43, 13 March 2023
- (sofern der Art entsprechend) Erforderliche Qualifikationen Der Use Case baut auf dem Use Case Fahrplanauskunft auf, das heißt für Dienste, die auf einer Fahrt3 KB (410 words) - 12:04, 18 July 2022
- capacity operational simulation tools use their own internal generic interlocking (table) model. Thus this use case does not require a interlocking table7 KB (959 words) - 14:06, 7 December 2023
- and print material as well as ticketing and real-time information. This use case will focus on the definition of the minimum requirements for passenger5 KB (751 words) - 13:28, 13 March 2023
- 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® 3 is not supposed to12 KB (1,475 words) - 15:28, 15 April 2024
- Description of parallel work is not included in this use case. For the purposes of this use case, the vehicle group is represented by vehicle types that6 KB (926 words) - 17:00, 4 December 2023
- IL:derailerIL (category Pages using Tabber parser tag)preferred position is the derailing one, which is automatically assumed after use. In addition the relation to the switch pt_swi03 is marked causing an5 KB (484 words) - 12:44, 27 May 2022
- with us. To learn where to find, how to use and how to contribute use cases see Dev:Use cases. While use cases follow a top-down approach, starting out5 KB (674 words) - 15:49, 15 April 2024
- Operational simulation; Betriebssimulation For various purposes it is necessary to simulate the process of railway operation for a fragment or an entire1 KB (146 words) - 13:29, 13 March 2023
- This use case covers the ordering of slots by Railway Undertakings from Infrastructure Manager(s) and other managers of capacity. A related use case will2 KB (273 words) - 13:26, 13 March 2023
- UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges (category Use case (TT)) (section Use case / Anwendungsfall)complete timetable for vehicle working scheduling_. Postcondition The train is changed within the validity of the change request, and unchanged outside.2 KB (209 words) - 18:11, 27 June 2022
- 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
- Main Page (section Infrastructure (IS))and track conditions. A list of use cases for the railML® infrastructure schema can be found on page Category:Use case (IS). →Main Article: Rollingstock10 KB (1,041 words) - 10:56, 2 May 2024
- this use case is the process description and the minimum data content for the timetable data exchange. The used data format is EDIFACT. The use case shall4 KB (592 words) - 18:06, 7 December 2023
- and Rostering Related subschemas: IS RS Reported by: PSI For general information on use cases see UC:Use cases6 KB (691 words) - 13:28, 13 March 2023
- commercial train elements.) A better modelling for this aspect is, in the author’s opinion, to use the concept of commercial trains in a different way than currently6 KB (688 words) - 13:26, 13 March 2023
- <rostering> is included, the element <rollingstock> is also required The elements <infrastructure> and <rollingstock> are master data for the use case "passenger9 KB (677 words) - 18:10, 27 June 2022
- IL:switchIL (category Pages using Tabber parser tag)type is called switchIL in railML interlocking subschema, whereas its counterpart in infrastructure is called switchIS. The switch is commonly used for19 KB (1,714 words) - 09:32, 3 May 2023
- Category:Use case (IS) (category Use cases)Use cases of the infrastructure subschema25 members (0 subcategories, 0 files) - 18:07, 20 November 2023
- for a railML® use case: A timetable for a competition (call for proposals) Ausschreibungsfahrplan The use case describes a timetable which is transferred16 KB (1,903 words) - 13:27, 13 March 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
- attributes. In case of consuming "wrong styled" id values the importing software is not required to extract semantics encoded in the id value. The use of this5 KB (463 words) - 12:22, 3 November 2023
- IL:reasonForConflict (category Pages using Tabber parser tag)value is used in case any signal that shall provide flank/head protection to either route is used as route destination for the other route, which is excluded520 bytes (9 words) - 18:50, 19 December 2019
- IL:movableCrossing (category Pages using Tabber parser tag)crossing whether this is physically needed or not. Subsequently the crossing as represented in the interlocking can have a position. In case of switch actuators15 KB (1,510 words) - 19:13, 14 February 2022
- Dev:Use case example/old (category Use case (unknown subschema)) (section Use case / Anwendungsfall)good use case. For an actual example see UC:IS:Schematic Track Plan. To get more information on use cases and how to describe them, see Dev:Use cases. Please2 KB (220 words) - 16:25, 4 December 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
- Information Category: Topology (origin: railML IS schema or classic track plan) Cable plan (origin: railML IS schema or classic track plan) infrastructure1 KB (119 words) - 13:51, 13 March 2023
- UC:IL:InterlockEngineeringForSignallingWithinJBV (category Use case (IL)) (section Use case / Anwendungsfall)The most normal in Norway is that whenever a change is made to the signalling system, the entire station is updated. This is defined as one interlocking5 KB (558 words) - 13:53, 13 March 2023
- UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (category Use case (TT)) (section Use case / Anwendungsfall)working data Typically, the import is done manually using a file based interface. Common Infrastructure: the import uses elements from mesoscopic and macroscopic3 KB (355 words) - 18:11, 27 June 2022
- UC:IL:SitePreparationDataForSignalControlledWarningSystems (category Use case (IL)) (section Use case / Anwendungsfall)signalkontrollierte Warnsysteme An SCWS is a system used to warn working gangs on used tracks that a train is arriving and that they have to stop their4 KB (571 words) - 13:51, 13 March 2023
- about restrictions concerning the infrastructure shall not be part of this use case ITMS. On the other hand a restriction of the infrastructure can be the16 KB (1,744 words) - 18:21, 13 May 2024
- IL:interlocking (category Pages using Tabber parser tag)register used. In case there is no officially used register the project-specific one shall be named with a leading underscore. The @id attribute is the “machine4 KB (493 words) - 10:38, 31 May 2021
- IS:mileageChange (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further2 KB (228 words) - 13:18, 17 April 2024
- features and therefore is not designed backward compatible. The most fundamental difference is difficult to recognize at the surface: It is based on RailTopoModel®3 KB (403 words) - 15:46, 15 April 2024
- IS:baliseGroup (category Pages using Tabber parser tag)regular accuracy towards the measured location is +/- 5m (locationAccuracy="5"). UNISIG-baseline 3 is in use (mVersion="32"). Corresponding railML® description:19 KB (2,555 words) - 16:55, 18 January 2024
- 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
- IL:tvdSection (category Pages using Tabber parser tag)section. It shall be used in case @isBerthingTrack is set to true. Within the simple example there are different kind of TVD sections. Here is a platform track7 KB (829 words) - 15:11, 27 May 2022
- value is used in case any signal that shall provide flank/head protection to either route is used as route destination for the other route, which is excluded2 KB (5 words) - 12:42, 8 February 2024
- RTM:anchor (category Pages using Tabber parser tag)<IS:mileageChange> page for the alternative approach, relevant for when there is a need for an explicit IS element. See the discussion in forum. Below you can see the source3 KB (269 words) - 17:11, 19 April 2024
- Attributes: preferredPosition: This is the preferred position of the switch which it is switched to when not in use or in case of both positions required for4 KB (5 words) - 14:21, 24 January 2020
- position. Switch throwing adds a delay to route setting that is of great interest to the use case simulation. For this purpose, we add an attribute typicalThrowTime4 KB (5 words) - 14:21, 24 January 2020
- position. Switch throwing adds a delay to route setting that is of great interest to the use case simulation. For this purpose, we add an attribute typicalThrowTime4 KB (5 words) - 14:21, 24 January 2020
- (line 2) It is recommended to use the XML comments for non-content related documentation, e.g. contact information: <!-- ... --> (line 4) It is recommended23 KB (2,659 words) - 09:51, 1 June 2022
- Attributes: preferredPosition: This is the preferred position of the switch which it is switched to when not in use or in case of both positions required for5 KB (5 words) - 12:41, 8 February 2024
- do not want to use an URL (Uniform Ressource Locator (external link)) as an identifier - since there is no real location - you can use any other Uniform7 KB (985 words) - 10:01, 1 June 2022
- IL:route (category Pages using Tabber parser tag)route definition is shown in the extract. It is a main route, which is not automatically set after first use. The time for route locking is given as 1 sec9 KB (1,077 words) - 08:15, 7 May 2022
- Dev:Using xsi:type (section How to use xsi:type)default namespace that is usually set to railML, an xsi:type attribute is necessary to indicate which particular type is meant. This is demonstrated above18 KB (2,309 words) - 14:28, 1 August 2022
- IL:levelCrossingIL (category Pages using Tabber parser tag)@maximumClosedTime – This is the time a level crossing is accepted by the interlocking as constantly closed before an alarm is raised. The value is needed by some18 KB (1,997 words) - 15:11, 4 June 2022
- certification is mandatory since the release of railML 2.2, all tools in productive use shall use *.railml for files / exports. *.xml is always allowed11 KB (1,742 words) - 18:13, 29 November 2023
- position. Switch throwing adds a delay to route setting that is of great interest to the use case simulation. For this purpose, we add an attribute typicalThrowTime5 KB (5 words) - 12:41, 8 February 2024
- position. Switch throwing adds a delay to route setting that is of great interest to the use case simulation. For this purpose, we add an attribute typicalThrowTime5 KB (5 words) - 12:41, 8 February 2024
- state is required. should – The state is the preferred one and should be used if possible (recommendation). must – The state must be used in any case (obligation)5 KB (613 words) - 01:23, 16 May 2024
- IL:keyLockIL (category Pages using Tabber parser tag)them is the key securely locked in and the other with the key released for removal. The key is a simple mean of authorisation transfer as its use allows4 KB (531 words) - 19:18, 29 January 2020
- IS:balise (category Missing Element Documentation/IS)of the balises. Conclusion: The use of railML® <balise> elements is optional. But if railML® <balise> elements are used, then the railML® <baliseGroup>8 KB (900 words) - 17:31, 11 April 2024
- IL:signalIL (category Pages using Tabber parser tag)release speed is a speed limit under which the train is allowed to run towards this signal, when the target speed is zero. This release speed is independent9 KB (1,314 words) - 10:15, 19 May 2023
- <rollingstock>, <timetable>. This attribute is to be used for the version number of the railML® schema the XML file is based on. Major, minor and corrigendum9 KB (1,043 words) - 11:28, 15 February 2023
- IL:key (category Pages using Tabber parser tag)hardware key that is related to physical lock. @isPhysical – The Boolean value gives indication whether the key is of physical type for use in a mechanical964 bytes (88 words) - 19:16, 29 January 2020
- IL:permissionZone (category Pages using Tabber parser tag)defining the zone is different. <canBeControlledBy> – This is the reference to any controller, i.e. operator/train dispatcher place, which can use the zone for1 KB (151 words) - 19:42, 29 January 2020
- 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:genericDetector (category Pages using Tabber parser tag)self-test of the detector. It has to be used in combination with @triggeredSelfTest. <detectorType> – This is the reference to the particular type of the2 KB (218 words) - 19:17, 29 January 2020
- IL:implementsSignalplan (category Pages using Tabber parser tag)and the slave is the start signal of the route. In case of signalling with stand-alone distant signals there is no master and the slave is the start signal17 KB (1,655 words) - 17:19, 30 January 2020
- element documentation using Template:Semcon, with status=proposed. Please also add the proposal to the list below! If a consensus is reached in the forum4 KB (579 words) - 16:49, 13 March 2023
- if the register is generally applicable and in practical use and maintenance by the registry is guaranteed. The further procedure is explained on the13 KB (721 words) - 14:12, 9 October 2023
- This is a meta-category referring to use cases. For a complete list of use cases see Category:AllUseCases or UC:Use cases.7 members (7 subcategories, 0 files) - 11:35, 18 July 2022
- towards the derailer when the derailer is in passablePosition. In such case the use of <hasPositionRestriction> is required. singleSwitchCrossing – works6 KB (912 words) - 14:29, 27 May 2022
- allows actualizing the codelists in very short cycles. The concept of codelists is explained here. The codelist consists of clearance gauge standards (external6 KB (294 words) - 14:03, 7 December 2023
- cycles. The concept of codelists is explained here. The list contains train protection systems (). The root element is named <trainProtectionSystems>. It11 KB (422 words) - 15:50, 16 November 2022
- IL:trainNumberField (category Pages using Tabber parser tag)a border, i.e. there is at one side no neighbouring section visible. @usedForDirection - The direction for which the field is used. This can be either both3 KB (348 words) - 13:08, 28 May 2022
- IL:movableBridge (category Pages using Tabber parser tag)<movableBridge> an <underCrossing> is seen, where a railway line is passed underneath by a waterway. This bridge is normally locked in the position for3 KB (405 words) - 15:00, 27 May 2022
- Category:Use case (IL) (category Use cases)Use cases of the interlocking subschema7 members (0 subcategories, 0 files) - 18:06, 20 November 2023
- IL:interface (category Pages using Tabber parser tag)@messString – This is the representation of the single messages status. The use is the same as for the @comString. A level crossing is a typical field element13 KB (1,119 words) - 17:46, 30 January 2020
- CO:positioning (category Pages using Tabber parser tag)gSystem>. It is used to locate infrastructure elements within the topology network. For the mesoscopic topology, it is recommended to use the classic railway11 KB (1,110 words) - 09:59, 29 April 2024
- IS:line (category Pages using Tabber parser tag)</linearLocation> ... </line> </lines> Suppose you want to make use of the intrinsic coordinates instead. In that case, you may leave out the linear positioning coordinates9 KB (873 words) - 11:03, 13 May 2024
- Category:Use case (RS) (category Use cases)Use cases of the rollingstock subschema2 members (0 subcategories, 0 files) - 18:07, 20 November 2023
- Category:Use case (TT) (category Use cases)Use cases of the timetable subschema15 members (0 subcategories, 0 files) - 18:07, 20 November 2023
- layout and formatting. This is useful for making more complex changes or for contributors who prefer working with markup directly. Use the “Preview” feature11 KB (1,424 words) - 18:13, 15 April 2024
- <designator> <name> <usesSymbol> <designator> <isLocatedAt> <name> <designator> <ellipticalProjection> <center> <designator> <name> <usesSymbol> <designator>188 KB (2,767 words) - 13:38, 4 December 2023
- Category:AllUseCases (category Use cases)This is a category of all use cases.51 members (0 subcategories, 0 files) - 11:30, 18 July 2022
- IL:routeExit (category Pages using Tabber parser tag)destination signal. <refersTo> – This is the reference to the physical end of the route path. This is in most cases a signal but can also be a buffer stop2 KB (187 words) - 20:37, 29 January 2020
- address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity errors. The concept is explained here. The list17 KB (299 words) - 15:10, 7 December 2023
- IS:border (category Pages using Tabber parser tag)element IS:border of railML® version 3.2 UML-visualization of IS Documentation A border point is used to separate the railway network due to different reasons706 bytes (9 words) - 18:23, 15 April 2024
- IL:hasTVDresetStrategy (category Pages using Tabber parser tag)and clearance sequence from a passing train is notified from the axle counter. In this case the section is reset immediately without any further operator4 KB (406 words) - 17:47, 22 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
- partialRouteReleaseDelay: Delay time after which the section may be released for use in a new route (obligatory; xs:duration), technology: the technical type of2 KB (5 words) - 14:21, 24 January 2020
- values: axleCounter: The TVD section is formed by axel counter detection points. trackCircuit: The TVD section is using track circuit equipment with insulated3 KB (5 words) - 12:41, 8 February 2024
- IL:assetsForInterlocking (category Pages using Tabber parser tag)of containers for elements to decribe their functional characteristics in use of the interlocking domain. These are track related, route related objects3 KB (359 words) - 13:19, 29 May 2022
- 1) Attributes: preferredPosition: This is the state of level crossing under normal conditions, i.e. when not in use. For most level crossings this would3 KB (5 words) - 14:21, 24 January 2020
- IL:activationCondition (category Pages using Tabber parser tag)level crossing is activated, i.e. requested to close for road traffic, upon train approach. There is a range of conditions to conclude a train is approaching4 KB (465 words) - 12:14, 30 May 2020
- IL:relatedMovableElement (category Pages using Tabber parser tag)UML-visualization of IL Documentation reference to other movable element in case of single/double slip switch or coupled switch Subschema interlocking Parents*524 bytes (5 words) - 18:47, 19 December 2019
- IL:tunnelGateIL (category Pages using Tabber parser tag)might be cases when the tunnel gate is normally blockingClosed and opened for railway traffic only on route setting. The normal closed status is used for tunnel5 KB (599 words) - 14:26, 27 May 2022
- IS:levelCrossingIS (category Missing Element Documentation/IS)Semantic Constraint "IS:003": <levelCrossingIS> should not have a <crossesElement> child of type railway. This case should be represented either1,015 bytes (15 words) - 11:37, 13 May 2024
- xs:duration), minimumOpenTime: This is the time the level crossing has to be open before it is allowed to close again. This is to ensure a certain capacity for4 KB (5 words) - 12:41, 8 February 2024
- 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
- Category:Use cases by company (category Use cases)28 members (28 subcategories, 0 files) - 11:37, 18 July 2022
- Category:Use case (unknown subschema) (category Use cases)3 members (0 subcategories, 0 files) - 11:38, 18 July 2022
- 15 members (0 subcategories, 0 files) - 16:45, 4 December 2023
File:PMM use case.png (773 × 415 (19 KB)) - 16:58, 19 December 2019File:PIS use case.png (762 × 195 (10 KB)) - 16:58, 19 December 2019File:IES use case.png (910 × 577 (29 KB)) - 16:58, 19 December 2019File:SCWS use case.jpg (610 × 530 (43 KB)) - 16:57, 19 December 2019File:IE use case.png (592 × 302 (31 KB)) - 16:58, 19 December 2019File:DAS use case.png (913 × 312 (26 KB)) - 16:56, 19 December 2019File:Interlocking use case.png (1,356 × 436 (173 KB)) - 16:58, 19 December 2019File:IE 2 use case.png (426 × 334 (21 KB)) - 16:57, 19 December 2019File:PMM use case 2.png (762 × 195 (15 KB)) - 16:58, 19 December 2019- <any> <coordinate> <name> <usesSymbol> <any> <isLocatedAt> <name> <linearElementProjection> <any> <coordinate> <name> <usesSymbol> <any> <isLocatedAt>125 KB (1,906 words) - 03:09, 26 October 2023
File:RailML UseCase Template.docx Template for use case description to be used by users for initial use case input(31 KB) - 17:43, 5 June 2023File:120px-PIS use case.png Importing file(120 × 31 (3 KB)) - 16:57, 19 December 2019File:120px-IE use case.png Importing file(120 × 61 (8 KB)) - 16:57, 19 December 2019File:240px-DAS use case.png Importing file(240 × 82 (12 KB)) - 16:56, 19 December 2019File:320px-IES use case.png Importing file(320 × 203 (38 KB)) - 16:56, 19 December 2019File:240px-SCWS use case.jpg Importing file(240 × 209 (8 KB)) - 16:56, 19 December 2019File:180px-Interlocking use case.png Importing file(180 × 58 (10 KB)) - 16:58, 19 December 2019File:180px-PIS use case.png Importing file(180 × 46 (5 KB)) - 16:57, 19 December 2019File:120px-SCWS use case.jpg Importing file(120 × 104 (3 KB)) - 16:57, 19 December 2019File:240px-PIS use case.png Importing file(240 × 61 (7 KB)) - 16:57, 19 December 2019File:320px-Interlocking use case.png Importing file(320 × 103 (22 KB)) - 16:57, 19 December 2019File:120px-Interlocking use case.png Importing file(120 × 39 (6 KB)) - 16:58, 19 December 2019File:799px-DAS use case.png Importing file(799 × 273 (55 KB)) - 16:57, 19 December 2019File:180px-SCWS use case.jpg Importing file(180 × 156 (5 KB)) - 16:57, 19 December 2019File:180px-DAS use case.png Importing file(180 × 62 (9 KB)) - 16:56, 19 December 2019File:240px-IES use case.png Importing file(240 × 152 (26 KB)) - 16:57, 19 December 2019File:240px-PMM use case.png Importing file(240 × 129 (18 KB)) - 16:57, 19 December 2019File:800px-IES use case.png Importing file(800 × 507 (119 KB)) - 16:58, 19 December 2019File:120px-DAS use case.png Importing file(120 × 41 (5 KB)) - 16:57, 19 December 2019File:320px-DAS use case.png Importing file(320 × 109 (17 KB)) - 16:57, 19 December 2019File:240px-IE use case.png Importing file(240 × 122 (21 KB)) - 16:58, 19 December 2019File:800px-DAS use case.png Importing file(800 × 273 (55 KB)) - 16:57, 19 December 2019File:120px-PMM use case.png Importing file(120 × 64 (7 KB)) - 16:57, 19 December 2019File:400px-Interlocking use case.png Importing file(400 × 129 (29 KB)) - 16:58, 19 December 2019File:180px-PMM use case.png Importing file(180 × 97 (12 KB)) - 16:57, 19 December 2019File:1200px-Interlocking use case.png Importing file(1,200 × 386 (143 KB)) - 16:57, 19 December 2019File:120px-IES use case.png Importing file(120 × 76 (10 KB)) - 16:57, 19 December 2019File:640px-IES use case.png Importing file(640 × 406 (92 KB)) - 16:57, 19 December 2019File:600px-Interlocking use case.png Importing file(600 × 193 (52 KB)) - 16:58, 19 December 2019File:180px-IE use case.png Importing file(180 × 92 (14 KB)) - 16:57, 19 December 2019File:180px-IES use case.png Importing file(180 × 114 (17 KB)) - 16:58, 19 December 2019File:800px-Interlocking use case.png Importing file(800 × 257 (80 KB)) - 16:58, 19 December 2019File:240px-Interlocking use case.png Importing file(240 × 77 (15 KB)) - 16:58, 19 December 2019File:Data Flows for Mainteanance Planning use case.png Figure 1(762 × 195 (11 KB)) - 16:58, 19 December 2019File:180px-PMM use case 2.png Importing file(180 × 46 (6 KB)) - 16:57, 19 December 2019File:120px-IE 2 use case.png Importing file(120 × 94 (11 KB)) - 16:57, 19 December 2019File:240px-IE 2 use case.png Importing file(240 × 188 (27 KB)) - 16:57, 19 December 2019File:120px-PMM use case 2.png Importing file(120 × 31 (4 KB)) - 16:57, 19 December 2019File:180px-IE 2 use case.png Importing file(180 × 141 (18 KB)) - 16:57, 19 December 2019File:240px-PMM use case 2.png Importing file(240 × 61 (9 KB)) - 16:57, 19 December 2019File:180px-640px-IES use case.png Importing file(180 × 114 (13 KB)) - 16:57, 19 December 2019File:180px-240px-IES use case.png Importing file(180 × 114 (15 KB)) - 16:57, 19 December 2019File:240px-Data Flows for Mainteanance Planning use case.png Importing file(240 × 61 (7 KB)) - 16:58, 19 December 2019File:120px-Data Flows for Mainteanance Planning use case.png Importing file(120 × 31 (3 KB)) - 16:58, 19 December 2019File:180px-Data Flows for Mainteanance Planning use case.png Importing file(180 × 46 (5 KB)) - 16:57, 19 December 2019- RS:administrativeData (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the RS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further521 bytes (38 words) - 21:53, 25 April 2022
- GML4RAILML:pos (category Pages using Tabber parser tag)this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the514 bytes (10 words) - 18:41, 19 December 2019
- Category:UC reported by IS (category Use cases by company)2 members (0 subcategories, 0 files) - 17:59, 20 March 2024
- RS:formation (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the RS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further512 bytes (38 words) - 16:19, 5 March 2021
- IL:routeEntry (category Pages using Tabber parser tag)changed. The start of a route is described in <routeEntry>. The element contains the following information: <refersTo> – This is the reference to the start1 KB (151 words) - 20:08, 29 January 2020
- Category:UC reported by Bombardier (category Use cases by company)1 member (0 subcategories, 0 files) - 17:58, 20 March 2024
- Category:UC reported by ERA (category Use cases by company)1 member (0 subcategories, 0 files) - 17:58, 20 March 2024
- Category:UC reported by Bahnkonzept (category Use cases by company)1 member (0 subcategories, 0 files) - 17:58, 20 March 2024
- Category:UC reported by SŽDC (category Use cases by company)1 member (0 subcategories, 0 files) - 17:52, 20 March 2024
- Category:UC reported by PSI (category Use cases by company)1 member (0 subcategories, 0 files) - 17:53, 20 March 2024
- Category:UC reported by JBD (category Use cases by company)1 member (0 subcategories, 0 files) - 17:53, 20 March 2024
- Category:UC reported by Interautomation (category Use cases by company)1 member (0 subcategories, 0 files) - 17:57, 20 March 2024
- Category:UC reported by EULYNX (category Use cases by company)1 member (0 subcategories, 0 files) - 17:58, 20 March 2024
- Category:UC reported by Thales (category Use cases by company)3 members (2 subcategories, 0 files) - 17:51, 20 March 2024
- Category:UC reported by Jernbanedirektoratet (category Use cases by company)1 member (0 subcategories, 0 files) - 17:47, 20 March 2024
- Category:UC reported by SMA (category Use cases by company)2 members (0 subcategories, 0 files) - 17:59, 20 March 2024
- Category:UC reported by Jernbaneverket (category Use cases by company)2 members (0 subcategories, 0 files) - 17:59, 20 March 2024
- Category:UC reported by IVU (category Use cases by company)2 members (0 subcategories, 0 files) - 17:59, 20 March 2024
- Category:UC reported by ÖBB (category Use cases by company)3 members (0 subcategories, 0 files) - 18:13, 20 March 2024
- Category:UC reported by ÖBB Personenverkehr (category Use cases by company)1 member (0 subcategories, 0 files) - 11:22, 18 July 2022
- Category:UC reported by iRFP (category Use cases by company)2 members (0 subcategories, 0 files) - 17:59, 20 March 2024
- Category:UC reported by DZSF & ZEDAS (category Use cases by company)1 member (0 subcategories, 0 files) - 17:58, 20 March 2024
- Category:UC reported by SNCF Réseau (category Use cases by company)1 member (0 subcategories, 0 files) - 17:52, 20 March 2024
- Category:UC reported by RailComplete (category Use cases by company)1 member (0 subcategories, 0 files) - 17:52, 20 March 2024
- Category:UC reported by Siemens Mobility (category Use cases by company)1 member (0 subcategories, 0 files) - 17:52, 20 March 2024
- Category:UC reported by ProRail (category Use cases by company)1 member (0 subcategories, 0 files) - 17:53, 20 March 2024
- Category:UC reported by railML (category Use cases by company)1 member (0 subcategories, 0 files) - 17:50, 20 March 2024
- Category:UC reported by HaCon (category Use cases by company)2 members (0 subcategories, 0 files) - 17:59, 20 March 2024
- Category:UC without specified reporter (category Use cases by company)15 members (0 subcategories, 0 files) - 18:13, 20 March 2024
- Category:UC reported by Jernbanedirektoratet/Bane NOR (category Use cases by company)1 member (0 subcategories, 0 files) - 17:53, 20 March 2024
- Category:UC reported by DLR for In2Rail project (category Use cases by company)1 member (0 subcategories, 0 files) - 17:58, 20 March 2024
- Category:UC reported by Czech Technical University in Prague (ČVUT) (category Use cases by company)1 member (0 subcategories, 0 files) - 17:58, 20 March 2024
- IL:situatedAtTrackAsset (category Pages using Tabber parser tag)of IL Documentation This is the reference to the track asset the danger point is located. It is used when the danger point is situated in the middle of523 bytes (5 words) - 18:51, 19 December 2019
- IL:hasLevelCrossingType (category Pages using Tabber parser tag)interlocking independently of the direction. This is the case for level crossings within stations. The level crossing is activated by route setting and deactivated3 KB (405 words) - 15:31, 29 October 2023
- IL:initStatus (category Pages using Tabber parser tag)Documentation The initial status of commands and messages on the interface in case of "cold start", i.e. a kind of predefined status to be assumed in absence513 bytes (0 words) - 18:48, 19 December 2019
- RS:vehicle (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the RS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further510 bytes (38 words) - 16:19, 5 March 2021
- IL:dangerPoint (category Pages using Tabber parser tag)the danger 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 supervised2 KB (232 words) - 20:39, 29 January 2020
- IL:combinedRoute (category Pages using Tabber parser tag)entry and exit of the route combination. The highest priority is 0. It is omitted if there is no alternative path. <designator> - A coded name as per a specified3 KB (348 words) - 12:05, 28 May 2022
- IL:hasAspect (category Pages using Tabber parser tag)cannot be cleared normally. In most cases such aspect is used with a special call-on route. caution – This is used for a distant signal aspect/slave aspect8 KB (1,085 words) - 10:48, 10 November 2023
- IL:routeStatusIndicator (category Pages using Tabber parser tag)@id - The unique identifier used to reference this element within railML. @positionInRoute - This marks whether the indicator is at the start or the end.2 KB (200 words) - 13:21, 28 May 2022
- Certify your interface. While you can use railML® in island solutions e.g. for exercise, in most cases productive use aims at and depends on exchanging data3 KB (371 words) - 17:02, 3 April 2023
- IS:functionalType (category Missing Element Documentation/IS)This element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further517 bytes (38 words) - 16:13, 5 March 2021
- TT:followupSections (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further519 bytes (38 words) - 21:54, 25 April 2022
- TT:identifier (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further513 bytes (38 words) - 21:55, 25 April 2022
- TT:origin (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further509 bytes (38 words) - 21:56, 25 April 2022
- TT:destination (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further514 bytes (38 words) - 21:56, 25 April 2022
File:Sctp2a.png Graph by Jernbaneverket for the SCTP Use Case(6,319 × 3,347 (142 KB)) - 16:57, 19 December 2019- IL:hasConfiguration (category Pages using Tabber parser tag)field elements is done by electric power. The interlocking logic is realised by relay circuits. electronic - The operation of field elements is done by electric3 KB (385 words) - 14:00, 21 August 2021
- Generic:places (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the generic subschema. It is available only in railML® 3.2. There exists an element <CO:places> that might514 bytes (58 words) - 12:42, 8 February 2024
- 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
File:RIND DataFlow.jpg Datenfluss zu Use Case Rail Inspection Data (RIND)(1,387 × 499 (86 KB)) - 13:22, 3 December 2023- location at the net element of a switch beginning. In this case, sw317a is located at ne3, and sw317b is located at ne30. Crossing then should be located with29 KB (2,876 words) - 14:34, 13 March 2024
- 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
File:Railway Simulation Laboratory.png Illustration for the use case Railway Simulation Laboratory: The current data flows concerning the trackside model infrastructure, rolling stocks and related(1,384 × 580 (199 KB)) - 16:58, 19 December 2019- CO:powerMode (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the CO subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further512 bytes (38 words) - 21:53, 25 April 2022
- TT:commercialTrainReference (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further527 bytes (38 words) - 21:56, 25 April 2022
- User:David Lichti/UC:?:Possessions (category Use case (unknown subschema)) (section Use case / Anwendungsfall)information. A possession is a temporary capacity reservation on some part of railway infrastructure for non-operational use. This causes restrictions4 KB (584 words) - 14:35, 16 May 2023
- 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
File:ETCS TrackNet DataFlows.png Data flows concerning the use case ETCS track net(457 × 136 (12 KB)) - 16:58, 19 December 2019- In this way, you inherit all information that is collected about the ÖBB in the code list, in this case name, country code and company code: <infrastructureManager6 KB (797 words) - 12:50, 29 November 2023
File:RailML3 SCTP DataFlows 160909.png Dataflows of the SCTP Use Case(457 × 211 (13 KB)) - 16:57, 19 December 2019- signal is a main signal within a station neither used for entry nor exit routes. intermediateStop: This is a special intermediate signal that is used for7 KB (5 words) - 12:41, 8 February 2024
- In this case, an ordinary switch is described, so the @navigability attribute is set to “both”. In other cases where only unidirectional travel is allowed18 KB (2,052 words) - 18:20, 15 April 2024
- and clearance sequence from a passing train is notified from the axle counter. In this case the section is reset immediately without any further operator2 KB (5 words) - 12:42, 8 February 2024
- itinerary point. Usually the section with the highest priority is used, however in case of operational requirement TMS may select among the others usually818 bytes (5 words) - 17:41, 15 January 2024
- designators as per manufacturer, owner, operator and keeper. This element is only useful in case of an individual vehicle. Subschema rollingstock Parents* vehicle680 bytes (5 words) - 21:53, 25 April 2022