|
|
| Line 1: |
Line 1: |
| {{useCase|IS|2.4|title=Passenger Information System|RS=1|TT=1|abbr=PISY}} | | {{mirror}} |
| | |
| {{UC title}}
| |
| Passenger Information System; {{Deu|Passagierinformationssystem}}; {{Fra|nom descriptif en Francais}}
| |
| | |
| {{UC 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.
| |
| | |
| {{UC flows}}
| |
| 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.
| |
| | |
| | |
| [[file:PIS use case.png|800px|Figure 1: Data flows for the Passenger Information System use case]]
| |
| | |
| {{UC interference}}
| |
| * rolling stock
| |
| * timetable
| |
| | |
| {{UC data}}
| |
| This section serves to specify the required data regarding certain aspects.
| |
| | |
| {{UC update}}
| |
| * Bulk transfer: regular changes 5-6 times a year
| |
| * Daily changes for incremental transfers
| |
| | |
| {{UC complexity}}
| |
| * Granularity of data: macro-level (operational points, lines)
| |
| * Complexity of data: railway line
| |
| | |
| {{UC focus}}
| |
| * Construction, more generally spoken "passenger information". Like construction areas and possible by-passes on the journey.
| |
| | |
| {{UC elements}}
| |
| * Macroscopic topology:
| |
| ** Lines
| |
| ** Operational points (stations)
| |
Revision as of 17:49, 24 November 2019