View source for UC:TT:TimetableInformation

{{useCase|TT|title=Timetable Information|IS=1|RS=1|RL=1|reporter=HaCon|abbr=TINF}}

{{UC title}}
Timetable Information; {{Deu|Fahrplanauskunft}}

{{UC description}}
Timetable information may include a range of passenger information systems such as a journey planner and print material as well as ticketing and real-time information. This use case will focus on the definition of the minimum requirements for passenger information. The required data includes stations, timetables, service categories. Furhtermore, data regarding links among stops and interchange times can be provided if available. This data would be provided by the long term planning (LTP) or short term planning (STP) timetabling tool. For short term changes/updates the focus lies on the data relevant for passengers information only (commercial view).

{{UC data}}
The data is provided according to the customer specific planning and subsequent publication processes. Usually fixed deadlines and timeframes exist for the typical planning horizons (please see below ''Which views are represented by the data (focus)?'').

{{UC interference}}
* infrastructure: {{IS:Tag|operationalPoint}}, {{IS:Tag|platform}}, {{IS:Tag|platformEdge}}
* rolling stock: {{RS:Tag|formation}} (?)
* interlocking: -

{{UC data}}
This section serves to specify the required data regarding certain aspects.

{{UC update}}
*''yearly'' for LTP planning
*''regular changes'' for STP planning
*''daily'' for VSTP planning

{{UC complexity}}
* whole data set: provide the full timetable
* full time window: provide full timetable for fixed time window (e.g. next 10 days only)
* changes for time window: provide only updated elements for a fixed time window (e.g. next 30 days)

{{UC focus}}
* LTP: the next yearly timetable - e.g. availability of the next yearly timetable 6 months ahead of time
* STP: short term planning changes to the current timetable - e.g. updated timetable information is provided for days +2 to +60

There is no fixed process for the exchange of data with a passenger information system. Whether or not it makes sense to identify and supply updates to a previous export file strongly depends on the capabilities of the systems involved (further discussion needed). Possible export options could be:
* '''Full''': a full timetable is provided for a specific time window
* '''Update''': only changes to the last export are provided for a specific time window (for the update process all files need to be handled in the correct sequence!)

{{UC elements|TT}}
As a bare minimum the commercial view of a train ({{TT:Tag|commercialTrain}} can be reduced to a {{TT:Tag|commercialTrainVariant}} referencing an {{TT:Tag|itinerary}} which via the reference to a {{TT:Tag|baseItinerary}} consists of a sequence of {{TT:Tag|baseItineraryPoint}} elements with commercially relevant stops ({{tag|TT|stop|baseItineraryPoint}} with an {{TT:Tag|isCommercial}} element). For the each stop the following data is shown:
* published times: {{TT:Tag|times}} element with scope='commercial'
* connections: {{TT:Tag|commercialConnection}} element(s)
* stop description: only {{tag|TT|stop|baseItineraryPoint}} elements which contain a {{TT:Tag|isCommercial}} elemente will be relevant including their {{tag|TT|activities|stop}} and possible additional {{tag|TT|activities|additionalStopInfo}} specified as {{tag|TT|additionalStopInfo|additionalStopInfos}} elements

In addition the following data would be useful for passenger information:
* platform
* passenger info texts
* announcements
* etc.


==Further Issues==
'''Handling of connections for partial exports'''

Depending on the process in the receiving system it might be necessary to provide only a single train with all the relevant connections. However, without the connected trains the current connection element is not valid and the referenced IDs cannot be used to map the connected trains/trainParts.

Update: with the release of railML 3.2 a version of railML has been published that includes a timetable subschema and fully supports partial updates and thus also the option to refer to another train that was transmitted earlier by its UUID.

'''Referencing platforms in the timetable'''

Currently the track and platform information shall be provided via the trackRef attribute linking the corrosponding element in the infrastructure. However, this requires quite a detailed infrastructure export. It should be possible to provide the commercial stations and platforms needed for the timetable export only.

Update: with the release of railML 3.2 a version of railML has been published that allows partial exports. This means that a railML with a train that references a certain platform does no long need to include that platform, but rather can refer to it directly using its UUID that was communicated with an earlier partial export that contained the infrastructure in a matching level of detail.

'''Handling of cancellations, partial cancellations, extra trains '''

Relevant changes to existing trains need to be represented in the export file. A complete list of changes needs to be defined. This will include the following changes:
* full cancellation of a train
* partial cancellation - i.e. of a trainPart
* extra train or trainPart
* cancelled stop
* extra stop
* etc.


'''Terms and Expressions'''
* LTP = '''l'''ong '''t'''erm '''p'''lanning: the yearly timetable(s)
* STP = '''s'''hort '''t'''erm '''p'''lanning: 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.)