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

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

and print material as well as ticketing and real-time information. This use case will focus on the definition of the minimum requirements for passenger

type is called switchIL in railML interlocking subschema, whereas its counterpart in infrastructure is called switchIS. The switch is commonly used for

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 signal

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 out

for a railML® use case: A timetable for a competition (call for proposals) Ausschreibungsfahrplan The use case describes a timetable which is transferred

and track conditions. A list of use cases for the railML® infrastructure schema can be found on page Category:Use case (IS). →Main Article: Rollingstock

Operational simulation; Betriebssimulation For various purposes it is necessary to simulate the process of railway operation for a fragment or an entire

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 this

complete timetable for vehicle working scheduling_. Postcondition The train is changed within the validity of the change request, and unchanged outside.

This use case covers the ordering of slots by Railway Undertakings from Infrastructure Manager(s) and other managers of capacity. A related use case will