Difference between revisions of "User talk:Milan Wölke"

From railML 2 Wiki
Jump to: navigation, search
m (Willkommen!)
 
Line 3: Line 3:
 
Möglicherweise möchtest du zunächst die [[Help:Inhaltsverzeichnis|Ersten Schritte]] lesen.
 
Möglicherweise möchtest du zunächst die [[Help:Inhaltsverzeichnis|Ersten Schritte]] lesen.
 
Nochmal: Willkommen und viel Spaß! [[Benutzer:Coordination|Coordination]] 11:21, 10. Mär. 2015 (CET)
 
Nochmal: Willkommen und viel Spaß! [[Benutzer:Coordination|Coordination]] 11:21, 10. Mär. 2015 (CET)
 +
 +
--------------------------------------------------------
 +
 +
1 railML® 3 use cases im timetable-Schema
 +
 +
Use case / Anwendungsfall / Scénario d’utilisation:
 +
 +
Passenger information at stations/Fahrgastinformation am Bahnhof
 +
 +
Description / Beschreibung / Description
 +
 +
This use case describes the exchange of data between a system for providing passenger information at a railway station and a timetable planning system. The PIS allows for display of the current schedule including information about the current state of operation such as delays, cancelation or additional trains. In order to do so the schedule as published to the passenger for the current day of operation is necessary. The completeness of this timetable information limits the accuracy of the information available to the passenger by means of the PIS. The mandatory data can be limited to the services run on the current operation day, including all stops of a train with the according arrival and departure times. Additional information for can be provided to model blocks of services (can be used to increase accuracy of forecast information), planned interconnection with other services, planned construction sites with impact on the services, etc.
 +
 +
Data Flows and Interfaces / Datenflüsse und Schnittstellen / Flux de données et interfaces
 +
 +
A PIS is a pure railML consumer.
 +
 +
Mandatory information imported from timetable system includes:
 +
• <train>
 +
• <trainPart>
 +
• <category>
 +
• <ocp>
 +
 +
 +
Optionally imported information includes:
 +
• <track>
 +
• <formation>
 +
• <annotation>/<annotationRef>
 +
• <rostering>
 +
• <connection> (in order to provide and manage connection information for internal or external services)
 +
• <statistics>
 +
 +
If the topology is not imported from railML it is assumed that it is imported from a different source including an appropriate mapping to the ocp’s imported from railML.
 +
 +
Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen / Interaction avec autres schemas railML®
 +
Mandatory: infrastructure
 +
Optionally: rolling stock
 +
 +
Characterizing Data / Charakterisierung der Daten / Caractérisation des données
 +
 +
This section serves to specify the required data regarding certain aspects.
 +
 +
How often do the data change (update)?
 +
yearly
 +
regular changes
 +
daily
 +
 +
How big are the data fragments to be exchanged (complexity)?
 +
Huge - whole data set
 +
 +
Which views are represented by the data (focus)?
 +
Mid term planning (eg. for yearly timetable disposition)
 +
Short term planning (eg. for trackworks)
 +
Passenger information
 +
 +
Which specific timetable data do you expect to receive/send (elements)?
 +
Element Mandato-ry Remarks
 +
Infrastructure/operationControlPoints/ocp X Used for referenc-ing with the PIS to-pology
 +
Timetable/timetablePeriods/timetablePeriod X
 +
Timetable/operatingPeriods/operatingPeriod X
 +
Timetable/categories/category
 +
Timetable/annotations/annotation
 +
Timetable/trainParts/trainPart/formationTT
 +
Timetable/trainParts/trainPart/operatingPeriodRef X
 +
Timetable/trainParts/trainPart/ocpsTT X
 +
Timetable/trainParts/trainPart/ocpsTT/times X
 +
Timetable/trainParts/trainPart/ocpsTT/connections
 +
Timetable/trainParts/trainPart/ocpsTT/statistics
 +
Timetable/trainParts/trainPart/ocpsTT/sectionTT/runTimes
 +
Timetable/trainParts/trainPart/ocpsTT/stopDescription
 +
Timetable/trainParts/trainPart/ocpsTT/stopDescription/stopTimes
 +
Timetable/trainParts/trainPart/ocpsTT/stopDescription/annotationRef
 +
Timetable/trainParts/trainPart/annotationRef
 +
Timetable/trains/train X
 +
Timetable/trains/train/trainPartSequence X
 +
Timetable/trains/train/trainPartSequence/trainPartRef X
 +
Timetable/rosterings/rostering/blockParts/blockPart
 +
Timetable/rosterings/rostering/blocks/block
 +
Timeta-ble/rosterings/rostering/blocks/block/blockPartSequence/blockPartRef

Revision as of 17:31, 15 March 2015

Willkommen bei Wiki.railML.org! Wir hoffen, dass du viele gute Informationen beisteuerst. Möglicherweise möchtest du zunächst die Ersten Schritte lesen. Nochmal: Willkommen und viel Spaß! Coordination 11:21, 10. Mär. 2015 (CET)


1 railML® 3 use cases im timetable-Schema

Use case / Anwendungsfall / Scénario d’utilisation:

Passenger information at stations/Fahrgastinformation am Bahnhof

Description / Beschreibung / Description

This use case describes the exchange of data between a system for providing passenger information at a railway station and a timetable planning system. The PIS allows for display of the current schedule including information about the current state of operation such as delays, cancelation or additional trains. In order to do so the schedule as published to the passenger for the current day of operation is necessary. The completeness of this timetable information limits the accuracy of the information available to the passenger by means of the PIS. The mandatory data can be limited to the services run on the current operation day, including all stops of a train with the according arrival and departure times. Additional information for can be provided to model blocks of services (can be used to increase accuracy of forecast information), planned interconnection with other services, planned construction sites with impact on the services, etc.

Data Flows and Interfaces / Datenflüsse und Schnittstellen / Flux de données et interfaces

A PIS is a pure railML consumer.

Mandatory information imported from timetable system includes: • <train> • <trainPart> • <category> • <ocp>


Optionally imported information includes: • <track> • <formation> • <annotation>/<annotationRef> • <rostering> • <connection> (in order to provide and manage connection information for internal or external services) • <statistics>

If the topology is not imported from railML it is assumed that it is imported from a different source including an appropriate mapping to the ocp’s imported from railML.

Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen / Interaction avec autres schemas railML® Mandatory: infrastructure Optionally: rolling stock

Characterizing Data / Charakterisierung der Daten / Caractérisation des données

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

How often do the data change (update)? yearly regular changes daily

How big are the data fragments to be exchanged (complexity)? Huge - whole data set

Which views are represented by the data (focus)? Mid term planning (eg. for yearly timetable disposition) Short term planning (eg. for trackworks) Passenger information

Which specific timetable data do you expect to receive/send (elements)? Element Mandato-ry Remarks Infrastructure/operationControlPoints/ocp X Used for referenc-ing with the PIS to-pology Timetable/timetablePeriods/timetablePeriod X Timetable/operatingPeriods/operatingPeriod X Timetable/categories/category Timetable/annotations/annotation Timetable/trainParts/trainPart/formationTT Timetable/trainParts/trainPart/operatingPeriodRef X Timetable/trainParts/trainPart/ocpsTT X Timetable/trainParts/trainPart/ocpsTT/times X Timetable/trainParts/trainPart/ocpsTT/connections Timetable/trainParts/trainPart/ocpsTT/statistics Timetable/trainParts/trainPart/ocpsTT/sectionTT/runTimes Timetable/trainParts/trainPart/ocpsTT/stopDescription Timetable/trainParts/trainPart/ocpsTT/stopDescription/stopTimes Timetable/trainParts/trainPart/ocpsTT/stopDescription/annotationRef Timetable/trainParts/trainPart/annotationRef Timetable/trains/train X Timetable/trains/train/trainPartSequence X Timetable/trains/train/trainPartSequence/trainPartRef X Timetable/rosterings/rostering/blockParts/blockPart Timetable/rosterings/rostering/blocks/block Timeta-ble/rosterings/rostering/blocks/block/blockPartSequence/blockPartRef