UC:TT:TrafficManagementPlan: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
No edit summary |
(Reporter added) |
||
Line 1: | Line 1: | ||
{{UseCase|TT|3.1|title=Traffic Management Plan}} | {{UseCase|TT|3.1|title=Traffic Management Plan|IS=1|RS=1|reporter=Thales Germany}} | ||
{{UC title}} | {{UC title}} | ||
Traffic Management Plan | Traffic Management Plan |
Revision as of 11:01, 2 April 2019
Traffic Management Plan Subschema: Timetable and Rostering Related subschemas: IS RS Reported by: Thales Germany | ||
| ||
For general information on use cases see UC:Use cases |
Use case / Anwendungsfall
Traffic Management Plan
Description / Beschreibung
Description / Beschreibung / Description The UseCase TrafficManagementPlan (TMP) defines exchange of information between Train Planning System (TPS) and Traffic Management System (TMS).
Data Flows and Interfaces / Datenflüsse und Schnittstellen
These data are relevant for both systems. Plans are transmitted from TPS to TMS. In situations where TPS is the single owner of the plan data, changes to the operational plan are transmitted back from the TMS to TPS. This enables the TPS to also work on VSTP level.
Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen
- Infrastructure
- <operationalType> (signal, station, tracks, stopPosition)
- Interlocking
- <routes>
- <overlap>, <dangerPoint>
- <flankProtection>
- RollingStock
- <formation>
- <trainOrder>
- <vehicleRef>
- <vehicle>
- <engine>
- <wagon>
Characterizing Data / Charakterisierung der Daten
How often do the data change (update)?
- yearly for LTP, VLTP
- regular changes for STP
- daily for VSTP
How big are the data fragments to be exchanged (complexity)?
- LTP, VLTP: big
- STP, VSTP updates: little
Which views are represented by the data (focus)?
- VLTP: Very long term planning
- LTP: Long term planning (e.g. for yearly timetable distribution)
- STP: Short term planning (e.g. for track works)
- Passenger information
Which specific data do you expect to receive/send (elements)?
- <train>
- <trainPartSequence>
- <trainPartRef>
- <trainPart>
- <formationTT>
- <operatingPeriodRef>
- <ocpsTT>
- <sectionTT>
- <runTimes>
- <connections>
- <stopDescription>
- <stopTimes>
- <sectionTT>
- <organizationalUnitBinding>
- <category>
- <operating Period>
- <operatingDay>
- <specialService>
- <timetablePeriod>
Glossary
- LTP = Long Term Planning: the yearly timetable(s)
- STP = Short Term Planning: changes to the current production timetable up to the point that changes can be published to downstream *systems (passenger information, train control, train operators, …)
- VLTP = Very Long Term Planning: >2 years
- VSTP = Very Short Term Planning: < 24 hours