UC:TT:TrafficManagementPlan: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(→‎Version numbers: railML 3.x added)
(TPS replaced by TCS and added to glossary (as discussed at TT-meeting in Linz on April 2nd, 2019))
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{UseCase|TT|3.x|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
{{UC description}}
{{UC description}}
Description / Beschreibung / Description
Description / Beschreibung / Description
The UseCase TrafficManagementPlan (TMP) defines exchange of information between Train Planning System (TPS) and Traffic Management System (TMS).
The UseCase TrafficManagementPlan (TMP) defines exchange of information between '''''Timetable Construction System''''' (TCS) and '''''Traffic Management System''''' (TMS).
{{UC flows}}
{{UC flows}}
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.
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}}
{{UC interference}}
*Infrastructure
*Infrastructure
Line 59: Line 59:
*VLTP = Very Long Term Planning: >2 years
*VLTP = Very Long Term Planning: >2 years
*VSTP = Very Short Term Planning: < 24 hours
*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 10:03, 2 April 2019

Traffic Management Plan
Subschema: Timetable and Rostering
 
Related subschemas: IS RS 
Reported by: Thales Germany
Stift.png (version(s) 3.1)
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 Timetable Construction System (TCS) and Traffic Management System (TMS).

Data Flows and Interfaces / Datenflüsse und Schnittstellen

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.

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>
    • <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. TPS from HaCon, Viriato from SMA, FBS from iRFP, ...)
  • TMS = Traffic Management System; a system which supports dispatching of trains on a network, mostly by IM, usually during a train run