TAF/TAP TSI

TAF/TAP TSI

General container for the different TAF/TAP TSI subareas. Shows the calendar of the different events on those subareas. 

Recent Activity

Filter 

April 20, 2023

March 6, 2023

  • Your profile picture
    2:09pm
    [TAF/TAP TSI] [] Mario Toma updated Additional value in the ReasonOfReference code list Monday, March 6Mario Toma updated Additional value in the ReasonOfReference code list   Changes to Modify the following element     *                   1016 = Same capacity need  *                   1016 = Same capacity need  -                               (Additional information: +                               (Reference to the Capacity -Reference to the previous train according to which the Capacity Needs +Needs Announcements from the previous year)* -Announcements was created)*                 *        . . .*           *        . . .* Mario Toma updated Additional value in the ReasonOfReference code list
    [TAF/TAP TSI] [] Mario Toma updated Additional value in the...

    [TAF/TAP TSI] [] Mario Toma updated Additional value in the ReasonOfReference code list

    Monday, March 6

    Mario Toma updated Additional value in the ReasonOfReference code list

     

    Changes to Modify the following element
     
    		 
     
    *                   1016 = Same capacity need 
    		 
    *                   1016 = Same capacity need 
    -
                                   (Additional information:
    		+
                                   (Reference to the Capacity
    -
    Reference to the previous train according to which the Capacity Needs
    		+
    Needs Announcements from the previous year)*
    -
    Announcements was created)*
    		  
     
    		 
     
              *        . . .*
    		 
              *        . . .*
    ...
    Changes to Modify the following element
     
    		 
     
    Read more

February 20, 2023

February 17, 2023

February 16, 2023

February 15, 2023

February 3, 2023

January 27, 2023

  • 4:05pm
    Nicolas Jasinski replied to Usage of particular runningstatus for Terminal events
    Usage of particular runningstatus for Terminal events

    Comment from Martin Schmidt (SBB Cargo International AG): 

     

    As SBB Cargo International we welcome the idea to integrate timestamps for intermodal transports in TAF TSI and with this in TRI message. Out of our perspective as RU the text provided in the CR under Purpose is misleading. We define the HLR as the moment when the train or wagon together with all documents are released for transport. Normally it is after the check of a wagon master but this depends on the terminal. It is the moment when the wagon or train is allowed to be moved out of the terminal.

    The MAD on the other hand is the moment when the wagon or train is handed over with all its documents to the terminal. This is after the arrival at the terminal and it’s the moment, when the legal responsibility is handed over to customer or terminal.

    Out of our perspective, there is no European wide agreed definition for HLR and MAD, because it depends on the partners, the type of transport and the local conditions.

    Because of this, we could not support the proposed solution and we would like to raise three objections:

    1. The proposed solution covers only single wagon transports and it’s not efficient for block trains.
    2. The proposed solution defines HLR and MAD on movements, which is not reflecting the local conditions and the contractual agreements.
    3. The proposed solution uses existing status, which could be misleading for other modes of transport and if the original purpose should be transmitted as well.

     

    We propose to add two new running status elements, which can be used for HLR and MAD independent from movement and as well as for trains and wagons.

     

December 20, 2022

December 16, 2022

Navigation

Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped

 
Your profile picture

Info on loco-charging in TrainActivity

 

Clarification of TrainActivity type codes 0044 to 0047 "connecting service"

 
This is a closed group. Only a group administrator can add you.