UC:TT:SlotOrdering: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
(+reporter)
 
({{mirror}})
Line 1: Line 1:
{{useCase|TT||title=Timetable Information|IS=1|RS=1|RL=1|reporter=SMA}}
{{mirror}}
 
{{UC title}}
Slot Ordering ; {{Deu|Trassenbestellung}}; {{Fra|nom descriptif en Francais}}
 
{{UC description}}
This use case covers the ordering of slots by Railway Undertakings from Infrastructure Manager(s) and other managers of capacity.
A related use case will be the slot offer by the Infrastructure Manager.
 
{{UC data}}
The data has to be provided by the Railway Undertaking to the relevant Infrastructure Managers.
 
{{UC interference}}
* infrastructure: {{IS:Tag|ocp}}
* rolling stock: {{RS:Tag|formation}} (?)
* interlocking: -
 
{{UC data}}
This section serves to specify the required data regarding certain aspects.
 
{{UC update}}
*''yearly'' for VLTP planning of frame contracts
*''yearly'' for LTP planning the regular timetable
*''regular changes'' for STP planning, e.g. for engineering infrastructure works, special event trains
*''daily'' for VSTP planning, e.g. strike, ad hoc freight trains
 
{{UC complexity}}
* Typically one train per order
* Maximum complexity is full timetable
 
{{UC focus}}
* Could be any of VLTP, LTP, STP, VSTP
* Covers the full train information, but for certain time periods
 
{{UC elements|TT}}
* Workflow information
** Not part of the timetable data
* Trains
** Identifier, e.g. {{TT:Tag|train}}.trainNumber
* Operating periods
* Train run {{TT:Tag|trainPart}}
** Earliest arrival
** Latest arrival
** Earliest departure
** Latest departure
** Minimum stop time
** Stop type, stop description
** Commercial connections
* Infrastructure {{TT:Tag|ocpTT}}
** Ordered stops
* Rolling stock  {{TT:Tag|formationTT}}
** Loco types
** Weight
** Length
** Maximum speed
** Infrastructure restrictions
 
{{UC elements|IS}}
As a minimum the {{TT:Tag|ocpTT}} elements with commercially relevant stops have to be listed in a {{TT:Tag|trainPart}}.  The <infrastructure> has to provide the related {{TT:Tag|ocp}} elements.
 
{{UC elements|RS}}
There is no mandatory requirement for detailed {{TT:Tag|vehicle}} information. The loco types may be used to identify performance characteristics and infrastructure restrictions by the Infrastructure Manager.
 
'''Terms and Expressions'''
* VLTP ='''v'''ery '''l'''ong '''t'''erm '''p'''lanning (>2 years)
* LTP = '''l'''ong '''t'''erm '''p'''lanning: the yearly timetable(s)
* STP = '''s'''hort '''t'''erm '''p'''lanning: < 1 year before operation
* VSTP = '''v'''ery '''s'''hort '''t'''erm '''p'''lanning: few days before operation

Revision as of 17:35, 24 November 2019

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

Template loop detected: Template:Mirror