UC:TT:UseCases: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
No edit summary
No edit summary
Line 13: Line 13:
* [[TT:UC:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings |Import complete timetable for vehicle working scheduling and vehicle workings; {{Deu|Umlaufbildung Fahrzeuge Jahresfahrplan}} ]]
* [[TT:UC:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings |Import complete timetable for vehicle working scheduling and vehicle workings; {{Deu|Umlaufbildung Fahrzeuge Jahresfahrplan}} ]]
* Dienstbildung Personal Jahresfahrplan
* Dienstbildung Personal Jahresfahrplan
* Umlauf an Jahresfahrplan anpassen
* [[TT:UC:AdoptVehicleWorkingSchedulingToTimetableChanges |Adopt vehicle working scheduling to timetable changes; {{Deu|Umlauf an Jahresfahrplan anpassen}} ]]
* [[TT:UC:ExchangeOfFormationData |Exchange of formation data; {{Deu|Austausch von Wagenreihungen/Behängungsdaten}} ]]
* [[TT:UC:ExchangeOfFormationData |Exchange of formation data; {{Deu|Austausch von Wagenreihungen/Behängungsdaten}} ]]
* Betriebssimulation Fahrplan
* Betriebssimulation Fahrplan

Revision as of 18:28, 21 May 2015

Use Cases for "Timetable and Rostering"

List of Use Cases

The following list provide links to the use cases related with the exchange of timetable data:

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, etc.)