UC:TT:TrafficManagementPlan: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
m (Ferri Leberl moved page TT:UC:TrafficManagementPlan to UC:TT:TrafficManagementPlan: Redirektauflösung)
 
({{mirror}})
Line 1: Line 1:
{{UseCase|TT|3.1|title=Traffic Management Plan|IS=1|RS=1|reporter=Thales Germany}}
{{mirror}}
{{UC title}}
Traffic Management Plan
{{UC description}}
Description / Beschreibung / Description
The UseCase TrafficManagementPlan (TMP) defines exchange of information between '''''Timetable Construction System''''' (TCS) and '''''Traffic Management System''''' (TMS).
{{UC flows}}
These data are relevant for both systems. Plans are transmitted from TCS to TMS. In situations where TCS is the single owner of the plan data, changes to the operational plan are transmitted back from the TMS to TCS. This enables the TCS to also work on VSTP level.
{{UC interference}}
*Infrastructure
**<operationalType> (signal, station, tracks, stopPosition)
*Interlocking
**<routes>
**<overlap>, <dangerPoint>
**<flankProtection>
*RollingStock
*<formation>
**<trainOrder>
**<vehicleRef>
*<vehicle>
**<engine>
**<wagon>
{{UC data}}
{{UC update}}
*yearly for LTP, VLTP
*regular changes for STP
*daily for VSTP
{{UC complexity}}
*LTP, VLTP: big
*STP, VSTP updates: little
{{UC 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
{{UC elements}}
*<train>
**<trainPartSequence>
**<trainPartRef>
*<trainPart>
**<formationTT>
**<operatingPeriodRef>
**<ocpsTT>
***<time>
***<sectionTT>
****<runTimes>
***<connections>
***<stopDescription>
****<stopTimes>
**<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
*TCS = Timetable Construction System; a system which develops planned timetables based on infrastructure and rolling stock data, used by RU and IM, usually '''before''' a train run; e.g. [https://www.hacon.de/loesungen/fahrplankonstruktion-und-management/ TPS] from [https://www.hacon.de/ HaCon], [https://www.sma-partner.com/de/loesungen/viriato-und-zlr/ Viriato] from [https://www.sma-partner.com/ SMA], [http://www.irfp.de/das-fahrplanbearbeitungssystem-fbs.html FBS] from [http://www.irfp.de/ iRFP], ...)
*TMS = Traffic Management System; a system which supports dispatching of trains on a network, mostly by IM, usually '''during''' a train run

Revision as of 17:31, 24 November 2019

🗒️ This page is mirrored from page UC:TT:TrafficManagementPlan in The railML® 2 wiki.  

Template loop detected: Template:Mirror