UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings: Difference between revisions
Jump to navigation
Jump to search
[unchecked revision] | [checked revision] |
({{mirror}}) |
(Versionfix) |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{ | {{useCase|TT|title=Import complete timetable for vehicle working scheduling and vehicle workings|CO=1|IS=1|RS=1|reporter=IVU}} | ||
{{UC title}} | |||
Import complete timetable for vehicle working scheduling and vehicle workings; {{Deu|Umlaufbildung Fahrzeuge Jahresfahrplan}} | |||
{{UC description}} | |||
A complete timetable shall be imported, serving as base for vehicle working scheduling. | |||
The following usecases are covered: | |||
* import infrastructure for vehicle working scheduling (optional) | |||
* import rolling stock data (optional) | |||
* import timetable for a calendar period | |||
* import timetable for an abstract regular week (template) | |||
* import partial vehicle working data | |||
{{UC flows}} | |||
Typically, the import is done manually using a file based interface. | |||
{{UC interference}} | |||
* Common | |||
* Infrastructure: the import uses elements from mesoscopic and macroscopic perspective | |||
* Rolling stock | |||
{{UC data}} | |||
{{UC update}} | |||
* static | |||
{{complexity}} | |||
* whole data set, or region | |||
{{UC focus}} | |||
* mid term | |||
{{UC elements}} | |||
====Timetable data==== | |||
* base data of commercial and operational trains (validity, train numbers, train category, train line, operators, concessionairs, subcontractors etc) | |||
* commercial train data | |||
** itineraries with optional platform assignments | |||
** commercial formation requirements (may vary per itinerary section), commercial coupling and branching | |||
** planned connection requirements with | |||
*** validity, source and target, minimum and maximum connection time, connection guaranteed flag, same platform required flag, connection direction (incoming, outgoing, both) | |||
* operational train data | |||
** references to commercial trains | |||
** itineraries with optional platform assignments | |||
** formations (may vary per itinerary section), including coupling and branching of trains | |||
====Infrastructure data==== | |||
Stops, stations, tracks, track sections. They should | |||
* refer to a ''validity'', possibly to be extended to daytime validity | |||
* carry infrastructure restrictions | |||
* allow computation of itineraries, including changes of direction | |||
====Rolling stock data==== | |||
Vehicle information should include | |||
* validity reference | |||
* length | |||
* weight | |||
* speed | |||
* traction | |||
* seating capacity (per class) | |||
* standing capacity | |||
* additional services (buffet, wlan, etc.) | |||
====vehicle working and rostering data==== | |||
Vehicle workings may be imported if there is a pre-planning that is to be completed. | |||
* Concatenation of operating trains to vehicle workings that are served by the same (abstract) vehicle | |||
* Shunting trips within OCPs (referencing microscopic infrastructure) | |||
* Non-revenue trains implementing operational needs | |||
* Maintenance blocks for abstract vehicles | |||
Rosterings may be imported if there is a pre-planning that is to be completed. | |||
The following data could be imported: | |||
* Assignment of a rostering plan to a depot | |||
* Concatenation of vehicle workings to multi-day sequences of trains served by the same (abstract) vehicle | |||
* depot runs | |||
* vehicle standbys | |||
* vehicle accounting for maintanance intervals | |||
==Open issues== | |||
* Identification of operational and commercial trains (if not present in railML data) | |||
* Relationship between operational and commercial trains (itineraries, formations, ...) |
Latest revision as of 18:11, 27 June 2022
Import complete timetable for vehicle working scheduling and vehicle workings Subschema: Timetable and Rostering Related subschemas: IS RS CO Reported by: IVU | ||
| ||
For general information on use cases see UC:Use cases |
Use case / Anwendungsfall
Import complete timetable for vehicle working scheduling and vehicle workings; Umlaufbildung Fahrzeuge Jahresfahrplan
Description / Beschreibung
A complete timetable shall be imported, serving as base for vehicle working scheduling.
The following usecases are covered:
- import infrastructure for vehicle working scheduling (optional)
- import rolling stock data (optional)
- import timetable for a calendar period
- import timetable for an abstract regular week (template)
- import partial vehicle working data
Data Flows and Interfaces / Datenflüsse und Schnittstellen
Typically, the import is done manually using a file based interface.
Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen
- Common
- Infrastructure: the import uses elements from mesoscopic and macroscopic perspective
- Rolling stock
Characterizing Data / Charakterisierung der Daten
How often do the data change (update)?
- static
- whole data set, or region
Which views are represented by the data (focus)?
- mid term
Which specific data do you expect to receive/send (elements)?
Timetable data
- base data of commercial and operational trains (validity, train numbers, train category, train line, operators, concessionairs, subcontractors etc)
- commercial train data
- itineraries with optional platform assignments
- commercial formation requirements (may vary per itinerary section), commercial coupling and branching
- planned connection requirements with
- validity, source and target, minimum and maximum connection time, connection guaranteed flag, same platform required flag, connection direction (incoming, outgoing, both)
- operational train data
- references to commercial trains
- itineraries with optional platform assignments
- formations (may vary per itinerary section), including coupling and branching of trains
Infrastructure data
Stops, stations, tracks, track sections. They should
- refer to a validity, possibly to be extended to daytime validity
- carry infrastructure restrictions
- allow computation of itineraries, including changes of direction
Rolling stock data
Vehicle information should include
- validity reference
- length
- weight
- speed
- traction
- seating capacity (per class)
- standing capacity
- additional services (buffet, wlan, etc.)
vehicle working and rostering data
Vehicle workings may be imported if there is a pre-planning that is to be completed.
- Concatenation of operating trains to vehicle workings that are served by the same (abstract) vehicle
- Shunting trips within OCPs (referencing microscopic infrastructure)
- Non-revenue trains implementing operational needs
- Maintenance blocks for abstract vehicles
Rosterings may be imported if there is a pre-planning that is to be completed.
The following data could be imported:
- Assignment of a rostering plan to a depot
- Concatenation of vehicle workings to multi-day sequences of trains served by the same (abstract) vehicle
- depot runs
- vehicle standbys
- vehicle accounting for maintanance intervals
Open issues
- Identification of operational and commercial trains (if not present in railML data)
- Relationship between operational and commercial trains (itineraries, formations, ...)