UC:IS:PassengerInformationSystem: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(insert of content)
 
(Standardization)
Line 1: Line 1:
'''Use case / {{Deu|Anwendungsfall}} / {{Fra|Scénario d’utilisation}}:'''
{{useCase|IS|2.3|title=Passenger Information System}}


{{UC title}}
Passenger Information System; {{Deu|Passagierinformationssystem}}; {{Fra|nom descriptif en Francais}}
Passenger Information System; {{Deu|Passagierinformationssystem}}; {{Fra|nom descriptif en Francais}}


 
{{UC description}}
'''Description / {{Deu|Beschreibung}} / {{Fra|Description}}'''
 
The application focuses the transfer of timetable, traction and topology information from the resource planning system of the railway infrastructure manager to the passenger information system of the same (or another) infrastructure manager.
The application focuses the transfer of timetable, traction and topology information from the resource planning system of the railway infrastructure manager to the passenger information system of the same (or another) infrastructure manager.


 
{{UC flows}}
'''Data Flows and Interfaces / {{Deu|Datenflüsse und Schnittstellen}} / {{Fra|Flux de données et interfaces}}'''
 
The data flow is one-directional: It goes from the resource planning system to the passenger information system.
The data flow is one-directional: It goes from the resource planning system to the passenger information system.
There are two types of data flows:
There are two types of data flows:
Line 19: Line 16:
[[Datei:PIS use case.png|Figure 1: Data flows for the Passenger Information System use case]]  
[[Datei:PIS use case.png|Figure 1: Data flows for the Passenger Information System use case]]  


 
{{UC interference}}
 
'''Interference with other railML<sup>®</sup> schemas / {{Deu|Interferenz mit anderen railML<sup>®</sup>-Schemen}} / {{Fra|Interaction avec autres schemas railML<sup>®</sup>}}'''
 
* rolling stock
* rolling stock
* timetable
* timetable


 
{{UC data}}
'''Characterizing Data / {{Deu|Charakterisierung der Daten}} / {{Fra|Caractérisation des données}}'''
 
This section serves to specify the required data regarding certain aspects.
This section serves to specify the required data regarding certain aspects.


<u>How often do the data change (update)?</u>
{{UC update}}
 
* Bulk transfer: regular changes 5-6 times a year
* Bulk transfer: regular changes 5-6 times a year
* Daily changes for incremental transfers
* Daily changes for incremental transfers


<u>How big are the data fragments to be exchanged (complexity)?</u>
{{UC complexity}}
 
* Granularity of data: macro-level (operational points, lines)
* Granularity of data: macro-level (operational points, lines)
* Complexity of data: railway line
* Complexity of data: railway line


<u>Which views are represented by the data (focus)?</u>
{{UC focus}}
 
* Construction, more generally spoken "passenger information". Like construction areas and possible by-passes on the journey.
* Construction, more generally spoken "passenger information". Like construction areas and possible by-passes on the journey.


<u>Which specific timetable data do you expect to receive/send (elements)?</u>
{{UC elements}}
 
* Macroscopic topology:
* Macroscopic topology:
** Lines
** Lines
** Operational points (stations)
** Operational points (stations)

Revision as of 18:14, 23 June 2016

Passenger Information System
Subschema: Infrastructure
Stift.png (version(s) 2.3)
For general information on use cases see UC:Use cases


Use case / Anwendungsfall

Passenger Information System; Passagierinformationssystem;

Description / Beschreibung

The application focuses the transfer of timetable, traction and topology information from the resource planning system of the railway infrastructure manager to the passenger information system of the same (or another) infrastructure manager.

Data Flows and Interfaces / Datenflüsse und Schnittstellen

The data flow is one-directional: It goes from the resource planning system to the passenger information system. There are two types of data flows:

  • Scenario 1: Bulk transfer of all (updated) timetable, traction and topology data: 5-6 times per year.
  • Scenario 2: Incremental transfer of short-term timetable, traction and topology data: Once a day.


Figure 1: Data flows for the Passenger Information System use case

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

  • rolling stock
  • timetable

Characterizing Data / Charakterisierung der Daten

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

How often do the data change (update)?

  • Bulk transfer: regular changes 5-6 times a year
  • Daily changes for incremental transfers

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

  • Granularity of data: macro-level (operational points, lines)
  • Complexity of data: railway line

Which views are represented by the data (focus)?

  • Construction, more generally spoken "passenger information". Like construction areas and possible by-passes on the journey.

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

  • Macroscopic topology:
    • Lines
    • Operational points (stations)
Retrieved from "https://wiki2.railml.org/index.php?title=UC:IS:PassengerInformationSystem&oldid=5193"