Search results

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 vehicle

Infrastructure Reported by: Bahnkonzept For general information on use cases see UC:Use cases

railML® for RINF Reporting; railML® für RINF Meldung This use case aims at providing a railML3 file, fulfilling the functional requirements published by

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 specialized

Advisory System (DAS); Fahrerassistentsystem The Driver Advisory System (DAS) is an on-train driver support system which advises a driver on the most energy-efficient

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 such

The infrastructure used in this use case is not based on the current infrastructure but an agreed future infrastructure state. It is important that any

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:

infrastructure is pulled from an asset management database. Future infrastructure is designed by hand from technical drawings. The timetable model is tested either

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 are

Interlocking Rollingstock The use case comprises static and dynamic (status) asset data. For infrastructure, the focus is only on static data. Small (operational

IS root element — IS use cases — Concepts & examples The railML® Infrastructure subschema is focused on the description of the railway network infrastructure

Current UML visualization A list of use cases for railML's interlocking scheme can be found here Category:Use_case_(IL). Interlocking Concepts — explanations

electrical simulation is not possible with the necessary accuracy without simulating the process of railway operation. Thus this use case is always an addon

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 that

capacity operational simulation tools use their own internal generic interlocking (table) model. Thus this use case does not require a interlocking table

preferred position is the derailing one, which is automatically assumed after use. In addition the relation to the switch pt_swi03 is marked causing an

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 shall

(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 Fahrt

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 to