UC:TT:TrafficManagementPlan

From wiki.railML.org
Jump to: navigation, search
Note.png This page is mirrored from page UC:TT:TrafficManagementPlan in The railML® 3 wiki.
Traffic Management Plan
Subschema: Timetable and Rostering
 
Related subschemas: IS RS 
Reported by: Thales Germany
Stift.png                   (version(s) 2.4)
For general information on use cases see UC:Use cases


Use case / Anwendungsfall / Scénario d’utilisation

Traffic Management Plan

Description / Beschreibung / Description

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 / Flux de données et interfaces

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 / Interaction avec autres schemas railML®

  • Infrastructure
    • <operationalType> (signal, station, tracks, stopPosition)
  • Interlocking
    • <routes>
    • <overlap>, <dangerPoint>
    • <flankProtection>
  • RollingStock
  • <formation>
    • <trainOrder>
    • <vehicleRef>
  • <vehicle>
    • <engine>
    • <wagon>

Characterizing Data / Charakterisierung der Daten / Caractérisation des données

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