User:Christian Rößiger

Use case / Anwendungsfall / :

Exchange of formation data; Austausch von Wagenreihungen/Behängungsdaten;

Description / Beschreibung /

What is the application behind the use case? Which data are required? Who or which tool/application provides these data? Which data are not included (if not obvious)? Define the boundaries of the use case and the relevant data. (max. 200 words, English)

Data Flows and Interfaces / Datenflüsse und Schnittstellen /

The usecase covers the exchange of the following data:

• the composition of <trainPart>s of <vehicle>s (using <formation>s)
• <operationalPeriod>s of <trainPart>s
• commercial and technical properties of <trainPart>s/<formation>s
• added and removed <trainPart>s within a <train>

The usecase does not cover the exchange of data concerning the <train>, e.g.

• changes of the train path or times (<ocpsTT>)
• added or removed <train>s

As a consequence, it is assumed that both source and target system of the exchanged data must refer to the same set of <train>s, i.e. the <train>s must have the same external identifier an identical train paths. Since the usecase mainly modifies existing objects in the target system, it is necessary that the railML data can be assigned to the correspoding objects in the target system. For this usecase the following railML object types

Interference with other railML^® schemas / Interferenz mit anderen railML^®-Schemen /

• infrastructure
• rolling stock
• interlocking
• other ..............

Characterizing Data / Charakterisierung der Daten /

This section serves to specify the required data regarding certain aspects.

How often do the data change (update)?

• static (not changing)
• yearly
• regular changes
• monthly
• weekly
• daily
• realtime (seconds)

How big are the data fragments to be exchanged (complexity)?

• tiny (attribute)
• very small (element)
• small (single train run)
• big (line)
• huge (region)
• whole data set (detailed operational concept network)

Which views are represented by the data (focus)?

• Long term planning (eg. for infrastructure dimensioning)
• Mid term planning (eg. for yearly timetable disposition)
• Short term planning (eg. for trackworks)
• Real term planning (eg. for dispatching)
• Statistics
• Fare collection
• Passenger information
• ...

Which specific timetable data do you expect to receive/send (elements)?

Fill in your application-specific data structure elements, which you are using and want to see modelled in railML 3.
Please describe also structures which should be modeled in another way (so called "code refactoring") in railML 3.
Attention: This is the most important part of this questionaire. Please define as detailed as possible, the length isn't limited here.