Search results

train number field, timetable element) to the next. For example, one use case is a TMS that provides the current (dispatching) timetable and train positions

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

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 exchange

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 part

offline simulation for capacity management. Implicitly, train dispatching is seen as a logical prolongation of a detailed timetable. At disruptions during

be assembled and visualised. For this purpose, railML infrastructure data is to be supplemented with basic information on the type, extent, and localization

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 as

signalling; CAD für Zugsignalisierung Engineers of the railway signaling discipline use a Computer-Aided Design (CAD) tool to model a railway construction project

Visualisation (RAIV) Subschema: Infrastructure For general information on use cases see UC:Use cases

will also be responsible for RINF Reporting to the European Union. This use case describes the current structure of the yearly report of ÖBB Infrastructure

other hand. It is a combination of defined organizational processes and a complete database application system. This database system is receiver and sender

von Schienenanlagen railML data will be used for engineering signalling and interlocking systems. Engineers are used to working with paper plans that schematically

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 basis

Schematic Track Plan Infrastructure managers use maps for the visualization of their railway infrastructure. These maps comprise: Geographic maps Geoschematic

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.pdf

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 the

the maintenance planning system of the infrastructure manager. The data flow is one-directional: It goes from the (central) asset management source data base

information system of the same (or another) infrastructure manager. The data flow is one-directional: It goes from the resource planning system to the passenger

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 this

access and use of the rail network (route network) of the infrastructure manager. It provides all the technical and operational information that is necessary