TEG TrainID – Use of UpdateLink- and ObjectInfoMessage and implications on TrainID DB Netz AG | I.NMF 11 | 12.02.2019

Is it possible for RUs to use UpdateLink- and ObjectInfo- Message to update TrainInfo without effect on elaboration? Situation The RU has a path (TypeOfInformation „booked“) for Monday to Friday from A to C via B at DB Netz for the whole validity period 2019 TrainID: TR/2180/--------RE99/00/2019 Dez 2018 to Dez 2019 Origin (X) (other IM) Destination (Y) (other IM) booked path from A to C via B at DB Netz Modification TrainInformation in planning process (Example): Case A: Change of destination in area of another IM for the whole validity period (Dez 2018 to Dez 2019). The RU wants to communicate the modification in the planning process to involved IMs. The booked path at DB Netz is not affected by the modification (no replanning needed). TrainID: TR/2180/--------RE99/01/2019 Dez 2018 to Dez 2019 Origin (X) (other IM) Destination (Z) (other IM) booked path from A to C via B at DB Netz Questions Is a new TrainID necessary because of changing destination? Is it possible to send an UpdateLinkMessage together with an ObjectInfoMessage to update a new TrainID and the destination, or does the modification of the TrainInformation inevitably result in a path cancellation with a following new path request? In this case IM has to check based on the rules of IM, if a new path elaboration is necessary or a new PathID is sufficient. DB Netz | 12.02.2019

Is it possible for RUs to use UpdateLink- and ObjectInfo- Message to split the validity period of booked path? Situation The RU has a path (TypeOfInformation „booked“) for Monday to Friday from A to C via B at DB Netz for the whole validity period 2019 TrainID: TR/2180/--------RE99/00/2019 Dez 2018 to Dez 2019 Origin (X) (other IM) Destination (Y) (other IM) booked path from A to C via B at DB Netz Modification TrainInformation in planning process (Example): Case B: Change of the destination in another country (other IM) for the second half of the validity period (July 2019 to Dez 2019). The RU wants to communicate the modification in the planning process to involved IMs. The booked path at DB Netz is not affected by the modification. TrainID: TR/2180/--------RE99/01/2019 Dez 2018 to June 2019 Origin (X) (other IM) DB Netz Destination (Y) (other IM) TrainID: TR/2180/--------RE99/02/2019 July 2019 to Dez 2019 Origin (X) (other IM) Destination (Z) (other IM) booked path: A to C via B at DB Netz Question Is a new TrainID for the first part of the validity period necessary due to new calendar or can the RU also use the same TrainID? Is it possible to use UpdateLink- and ObjectInfoMessage to split validity period of train object or is path cancellation with two new path requests necessary? Note: In our opinion the path object has to split in two paths, because it is not allowed to link one path object with two train objects. Furthermore, the ObjectInfoMessage does not allow to create a new object (no suitable ObjectTypeCode). DB Netz | 12.02.2019

Proposal for clarification or definition Change of link between object train and object path is allowed only for whole objects and their whole validity period Usage of UpdateLink- and ObjectInfoMessage is allowed only to change an object for whole validity period Note: If it is possible to use UpdateLink- and ObjectInfoMessage to split validity period of train object we need a new ObjectTypeCode (for example: “Creation”) to create a new object. Changes of objects lying in the past is forbidden Is a new TrainID necessary because of changing destination? Is a new TrainID necessary, if the calendar has changed or can the RU also use the same TrainID? (Compare the decision to handling with the PathID in case of changing Calendar in PathInformation --> same PathID) Note: According to current statements it is not allowed to change the train object and TrainID in the modification process, therefore the option of the modification process was not considered. DB Netz | 12.02.2019

THANK YOU!