Difference between revisions of "UC:TT:UseCases"

From wiki.railML.org
Jump to: navigation, search
[unchecked revision][unchecked revision]
Line 18: Line 18:
 
* Disposition Fahrzeugeinsatz (<font color="red">writer: ???</font color>; <font color="red">reviewer: ???</font color>)
 
* Disposition Fahrzeugeinsatz (<font color="red">writer: ???</font color>; <font color="red">reviewer: ???</font color>)
 
* Ergebnis Fahrplansimulation (<font color="red">writer: ???</font color>; <font color="red">reviewer: ???</font color>)
 
* Ergebnis Fahrplansimulation (<font color="red">writer: ???</font color>; <font color="red">reviewer: ???</font color>)
* [[TT:UC:FGIInTrain|Fahrgastinformation im Zug (<font color="red">writer: PSI</font color>; <font color="red">reviewer: iRFP</font color>)]]
+
* [[TT:UC:FGIInTrain|Fahrgastinformation im Zug (<font color="green">writer: PSI</font color>; <font color="red">reviewer: iRFP</font color>)]]
 
* Betriebsleitsysteme/RBL (<font color="red">writer: INIT or Interautomation</font color>; <font color="red">reviewer: IVU</font color>)
 
* Betriebsleitsysteme/RBL (<font color="red">writer: INIT or Interautomation</font color>; <font color="red">reviewer: IVU</font color>)
 
* Dienstbildung Personal Jahresfahrplan (<font color="red">writer: INIT</font color>; <font color="red">reviewer: IVU</font color>)
 
* Dienstbildung Personal Jahresfahrplan (<font color="red">writer: INIT</font color>; <font color="red">reviewer: IVU</font color>)

Revision as of 17:40, 11 December 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.)