1. Modelling of Train and Path in TAF/TAP TSIs
Planning/TRID TEG, 07/05/2019
FTE, TrID WG, 08/05/2019
Christian Weber, SNCF
Version 0.4 of 07/05/2019

2. Agenda
Main objects and attributes
Life cycle
Data model

3. Agenda
Main objects and attributes
Life cycle
Data model

4. What are the main objects and attributes for planning and operation ?
PLANNED TRAIN NUMBER (PTN) is the "short number" used by RU to identify the train during RU harmonisation (in PCS, field currently named "International Train Number").
PATH is the space-time allocated by IM to RU. Identified by PAID decided by the IM 5 3 6
Köln 1
COMMERCIAL TRAIN NUMBER (CTN) is the number used for passengers information (e.g. on the reservation ticket, display in stations). The CTN is allocated by the RU and used by the RU and the SM (Station Manager)
Amsterdam
TRAIN is the "move offer" foreseen by RU. Identified by TRID allocated by the RU at the beginning of the path allocation
INFRASTRUCTURE TRAIN NUMBER (ITN) is the "short number" used by IM to identify the national path and usually the assembled path according to UIC leaflets 419-1/2
Bruxelles 7
Paris
Object
Time
PATH REQUEST is a request by RU to IM to receive a path to operate the train. Identified by PRID allocated by the RU 2
Attribute
CASE REFERENCE is a workflow document used for one path request or a set of path requests gathered for organisational reasons. Identified by CRID allocated by the RU (or the IM for internal purposes)
OPERATIONAL TRAIN NUMBER (OTN) is the "short number" used by IM and RU in daily operation (e.g. display in signalling box, communication signalling box/train). Allocated by the IM, it is usually equal to ITN and can be changed in case of event in operation 4 8

5. Description of the objects
Objects and Identifiers - Overview
Four objects are defined currently
Train ("owned" by the Railway Applicant [RA])
Path Request ("owned" by the RA)
Path ("owned" by the IM)
Case Reference cf. Dossier ("owned" by the RA, IM, other actors)
These objects are not explicitely defined in the TAP/TAF data model (xsd) but implicitely defined in the messages
The data model will be proposed at the end of the presentation
TRID, PRID, PAID, CRID have a common structure :
Object Type (2A)
Company Code (4AN)
Core Element (12AN)
(free content decided by the Lead RU)
Variant (2AN)
Yearly Timetable (4N)
Date (8N) TR
1187
--PAR_AMS_03 01
2017
Planning (with calendar/regime) : 24 AN
Operation (with day of running) : 32 AN

6. Agenda
Main objects and attributes
Life cycle
Data model

7. Life cycle Which IDs and Objects are used in the life cycle ?
Simplified life cycle
Example with 2 RUs and 2 IMs
Three steps :
Path request
Change after path is allocated (booked)
Train preparation and operation (running)
Nota : For simplification, PTN, CTN, ITN are not considered in this presentation

8. Life cycle Path request phase (1/4) There is 1 TRAIN (to request)
Lead RU = RU1
RU1
RU2
Train TRID1
TrainInfo
Orig. 08:00
Bord. 10:00
Dest. 12:00
Mo to Su
Path Req. PRID1
TrainInfo
PathInfo
Orig. 08:00
Bord. 10:00
Mo to Su
Path Req. PRID2
TrainInfo
PathInfo
Bord. 10:00
Dest. 12:00
Mo to Su
Lead RU = RU1
Train TRID?
TrainInfo1
Orig. 08:15
Bord. 10:15
Dest. 12:15
Mo to Th
IM1
IM2
Train TRID?
TrainInfo2
Orig. 08:15
Bord. 10:15
Bord
Dest. 12:30 Fr
Train TRID?
TrainInfo3
Orig. 08:30
Bord. 10:30
Dest. 12:30
Sa to Su
Path PAID1
PathInfo1
Orig. 08:15
Bord. 10:15
Mo to Fr
Path PAID2
PathInfo2
Orig. 08:30
Bord. 10:30
Sa to Su
Path PAID3
PathInfo3
Bord. 10:15
Dest. 12:15
Mo to Th
Path PAID4
PathInfo4
Bord. 10:30
Dest. 12:30
Fr to Su
There is 1 TRAIN (to request)
There are 3 TRAINS (to produce)
How can it be managed ?

9. Life cycle Path request phase (2/4) Easy to manage For the IMs
There are 4 PATHS to produce
Capacity check on line and in stations
Programming of the signalling boxes
Traffic management
Etc.
How to manage ?
For the RUs
There is 1 TRAIN to request
There are 3 TRAINS to produce
Rostering (rolling stock, drivers, conductors, etc.)
Resources allocation
Information for passengers (timetabling, digital tools, ticketing, display in stations and trains, etc.)
Information for freight customers
Etc.

10. How to manage 1 TRAIN to request and 3 TRAINS to produce ?
Life cycle
Path request phase (3/4)
How to manage 1 TRAIN to request and 3 TRAINS to produce ?  
Create new TRIDs and inform via Update Link Message
Numerous updates
Complex process
Difficult IT implementation 
TRID kept
Object TRAIN TO PRODUCE = TRID (ID only) + relevant PATH objects (PAID + PathInfo)
The TRAIN TO PRODUCE remains virtual and is NOT a real object
Should be generated dynamically
Complex to manage
Difficult IT implementation
TRID1 
PAID1
In IM1
Mo-Fr
PAID2
In IM1
Sa-Su
PAID3
In IM2
Mo-Th
PAID4
In IM2
Fr-So 
TRID kept
One TRAIN object with several TrainInfo elements (1 TI elt for request extended to 3 TI elts after allocation)
Each TrainInfo element receives an ID (e.g. 2 AN) -> format 26 AN for objet TRAIN TO PRODUCE
Add TrainInfo elements after answer
Object Info Message to be sent
Different formats
Numerous updates
Complex process
Difficult IT implementation  
TRID kept
Create a new object (e.g. TRAIN PRODUCTION) used only by the RUs
This object is implemented by the RUs
Object TRAIN PRODUCTION
TPID (24 AN or 32 AN daily)
TRID
TrainInfo (1 element)
Created after allocation by the LeadRU and sent to the other RUs via ObjectInfoMessage
Easy to implement
Principle of TRID kept
Object TP managed only by RUs
No Update Link to send 

11. Life cycle Path request phase (4/4)
Lead RU = RU1
RU1
RU2
Train TRID1
TrainInfo
Orig. 08:00
Bord. 10:00
Dest. 12:00
Mo to Su
Path Req. PRID1
(TRID1)
PathInfo
Orig. 08:00
Bord. 10:00
Mo to Su
Path Req. PRID2
(TRID1)
PathInfo
Bord. 10:00
Dest. 12:00
Mo to Su
Lead RU = RU1
Train TPID1 (TRID1)
TrainInfo
Orig. 08:15
Bord. 10:15
Dest. 12:15
Mo to Th
Train TPID2 (TRID1)
TrainInfo
Orig. 08:15
Bord. 10:15
Bord
Dest. 12:30 Fr
Train TPID3 (TRID1)
TrainInfo
Orig. 08:30
Bord. 10:30
Dest. 12:30
Sa to Su
IM1
IM2
Path PAID1
(TRID1)
PathInfo
Orig. 08:15
Bord. 10:15
Mo to Fr
Path PAID2
(TRID1)
PathInfo
Orig. 08:30
Bord. 10:30
Sa to Su
Path PAID3
(TRID1)
PathInfo
Bord. 10:15
Dest. 12:15
Mo to Th
Path PAID4
(TRID1)
PathInfo
Bord. 10:30
Dest. 12:30
Fr to Su
3 TRAIN PRODUCTION (with 3 TPIDs) to produce linked to the same TRID

12. Life cycle Objects TRAIN and PATH when the path is booked
Content of the IMs and RUs IT systems when the path is booked at the end of the path request phase
Train rq TRID1
TrainInfo
Orig. 08:00
Bord. 10:00
Dest. 12:00
Mo to Su
Path PAID1
(TRID1)
PathInfo
Orig. 08:15
Bord. 10:15
Mo to Fr
Path PAID2
(TRID1)
PathInfo
Orig. 08:30
Bord. 10:30
Sa to Su
Path PAID3
(TRID1)
PathInfo
Bord. 10:15
Dest. 12:15
Mo to Th
Path PAID4
(TRID1)
PathInfo
Bord. 10:30
Dest. 12:30
Fr to Su
RU1
RU1
RU2
RU2
RU1
RU2
IM1
IM1
IM2
IM2
IM1
Train op TPID1
(TRID1)
TrainInfo
Orig. 08:15
Bord. 10:15
Dest. 12:15
Mo to Th
Train op TPID2
(TRID1)
TrainInfo
Orig. 08:15
Bord. 10:15
Bord
Dest. 12:30 Fr
Train op TPID3
(TRID1)
TrainInfo
Orig. 08:30
Bord. 10:30
Dest. 12:30
Sa to Su
IM2
RU1
RU1
RU1
RU2
RU2
RU2

13. Life cycle Exchange of objects and IDs for path change (1/2)
Focus on objects TRAIN and PATH (not on PATH REQUEST and C.REF)
In case of path modification (by RUs) or alteration (by IMs), the objects and/or IDs hereafter are used in the message exchange between :
IM1-IM2
IM1-RU1
IM2-RU2
RU1-RU2
The processes are already described and known
IDs and Objects exchanged for path change for IM-IM, IM-RU and RU-RU messages
TRID1 is always included in the messages
Train rq TRID1
TrainInfo
Orig. 08:00
Bord. 10:00
Dest. 12:00
Mo to Su
Path PAID1
(TRID1)
PathInfo
Orig. 08:15
Bord. 10:15
Mo to Fr
Path PAID2
(TRID1)
PathInfo
Orig. 08:30
Bord. 10:30
Sa to Su
Path PAID3
(TRID1)
PathInfo
Bord. 10:15
Dest. 12:15
Mo to Th
Path PAID4
(TRID1)
PathInfo
Bord. 10:30
Dest. 12:30
Fr to Su
RU1
RU1
RU1
RU2
RU2
RU2
IM1
IM1
IM1
IM2
IM2
IM2

14. Life cycle Exchange of objects and IDs for path change (2/2)
If the change has an impact on the object TRAIN PRODUCTION, they are updated by the LRU when the change is finalized
Example : The change modifies the timing on Sunday
RU1 (LRU) :
updates the Train Production 3 (Sa only)
creates the Train Production 4 (for Su)
sends the update to RU2
Nota : TRID1 is always included in the messages
Train op TPID1
(TRID1)
TrainInfo
Orig. 08:15
Bord. 10:15
Dest. 12:15
Mo to Th
Train op TPID2 (TRID1)
TrainInfo
Orig. 08:15
Bord. 10:15
Bord
Dest. 12:30 Fr
Train op TPID3
(TRID1)
TrainInfo
Orig. 08:30
Bord. 10:30
Dest. 12:30 Sa
Train op TPID4
(TRID1)
TrainInfo
Orig. 08:30
Bord. 10:30
Dest. 12:45 Su
The updated objects TP3 and TP4 are used to update :
the information for customers
the rosters (driver, rolling stock, etc.)
RU1
RU1
RU1
RU1
RU2
RU2

15. Life cycle Exchange of objects and IDs in preparation and operation
In train preparation phase and train operation phase, the objects and/or IDs hereafter are used in the message exchange between :
IM1-IM2
IM1-RU1
IM2-RU2
RU1-RU2
The processes are already described and known
Train rq TRID1+Day
OTN
RU1
RU2
RU1
RU2
IM1
IM2
IM1
IM2
The IMs retrieve the daily PAID and the PATHvia TRID1+Day
The RUs retrieve the daily TPID and the TRAIN PRODUCTION via TRID1+Day

16. Life cycle with Train Production object
Same characteristics, same Train Production objects (1/2)
RU1
RU1
RU1 wants two trains:
one for working days
one for week-ends
Train TRID1
TrainInfo
Orig. 08:15
Dest. 12:15
Mo to Fr
Path Req. PRID1
(TRID1)
PathInfo
Orig. 08:15
Dest. 12:15
Mo to Fr
Train TRID2
TrainInfo
Orig. 08:30
Dest. 12:30
Sa to Su
Path Req. PRID2
(TRID2)
PathInfo
Orig. 08:30
Dest. 12:30
Sa to Su
IM1
RU1
The answer is two trains:
one for working days
one for week-ends
same than the wish
Path PAID1
(TRID1)
PathInfo
Orig. 08:15
Dest. 12:15
Mo to Fr
Train
TPID1 (TRID1)
TrainInfo
Orig. 08:15
Dest. 12:15
Mo to Fr
Path PAID2
(TRID2)
PathInfo
Orig. 08:30
Dest. 12:30
Sa to Su
Train
TPID2 (TRID2)
TrainInfo
Orig. 08:30
Dest. 12:30
Sa to Su

17. Life cycle with Train Production object
Same characteristics, same Train Production objects (2/2)
RU1
RU1
RU1 wants one train :
the same for all days
Train TRID1
TrainInfo
Orig. 08:00
Dest. 12:00
Mo to Su
Path Req. PRID1
(TRID1)
PathInfo
Orig. 08:00
Dest. 12:00
Mo to Su
RU1
IM1
Train
TPID1 (TRID1)
TrainInfo
Orig. 08:15
Dest. 12:15
Mo to Fr
Train
TPID2 (TRID1)
TrainInfo
Orig. 08:30
Dest. 12:30
Sa to Su
Path PAID1
(TRID1)
PathInfo
Orig. 08:15
Dest. 12:15
Mo to Fr
Path PAID2
(TRID1)
PathInfo
Orig. 08:30
Dest. 12:30
Sa to Su
The answer is two trains :
one for working days
one for week-ends
different of the wish
In both cases the objects TRAIN PRODUCTION to be produced by the RU are the same even the process to create them is different

18. The object type ‘TP’ should be reserved for the TRAIN Production
Life cycle with Train Production object
To summarize (2/2)
Easy life for the RUs with a new object TRAIN PRODUCTION used only by RUs
The Lead RU creates the object TRAIN PRODUCTION and informs the other RUs (normally via the Object Info Message)
The object TRAIN PRODUCTION is used inside the RUs and is the basis for RU production (rostering, customers information, etc.)
The TRID is unchanged during the complete process
No need to update the object TRAIN (to request) even when the answer of the IMs is different of the request of the RUs
TRID continues to be used in the messages (RU/IM, IM/IM, RU/RU)
No need for the RUs to send the object TRAIN PRODUCTION to the IMs
The phase of request and the phase of production are mirrored
PATH REQUEST and PATH (to produce)
TRAIN (to request) and TRAIN PRODUCTION (to produce)
The object type ‘TP’ should be reserved for the TRAIN Production

19. Agenda
Main objects and attributes
Life cycle
Data model

20. Draft data model with the messages and the 5 objects TR, PA, PR, TP, CR
CASE REFERENCE (CRID)
TRAIN PRODUCTION
TrainProduction ID (TPID) [1]
PathRequestMessage
TrainID (TRID) [1]
Header [1]
PathID (PAID) [1-n]
TRAIN (REQUEST)
TrainID (TRID) [1]
TrainInformation [1]
Composition
Locations with Timing
Calendar
OTN**
Etc.
PathInformation [1]
Composition
Locations with Timing
Calendar
OTN**
Etc.
TrainInformation [1]
Composition
Locations with Timing
Calendar
OTN*
Etc.
PATH
REQUEST
Header [1]
PathRequestID (PRID) [1]
PATH
TrainID (TRID) [1]
PathID (PAID) [1]
PathInformation [1]
Composition
Locations with Timing
Calendar
OTN*
Etc.
PathInformation [1]
Composition
Locations with Timing
Calendar
OTN**
Etc.
TrainID (TRID) [1]
PathDetailsMessage
PathRequestID (PRID) [1]
* wished/proposed by the RU
** allocated by the IM
[x] cardinality (1 or n)
The cardinality (1,1 – 1,n – n,n) between the objects (e.g. between TRAIN and PATH) is not indicated here