We are committed to improving our services continuously. A number of improvements have been implemented within HCN Rail recently, based on customer feedback. This email summarises those improvements.
Container data change retrieval in Train Composition template
Instead of using handlingID, you can now retrieve container data in the train composition template using the container number. The HCN Rail web screens allow you to share the train composition with the terminal via the Train Composition template. If the train composition lists a container for pick up/drop off at a terminal connected to HCN Rail, you can now also retrieve the container data based on the container number. Previously, this was only possible using the handlingID. This improvement makes it easier to use the Train Composition function for users of the HCN Rail web screens. Please note that if containers are loaded using their reference, you must use the handlingID to retrieve the container data. Please refer to the Quick Start Guide and the first tab of the Train Composition template for more information.
Train number validation
The train number will be validated as of 20 november. The development of the ETA Train functionality is currently in full swing. In the ETA Train function, the train number is used to retrieve up-to-date information about the location of the train. At present, it is mandatory to input the train number. However, invalid train numbers are often communicated by the rail operators. In preparation for the ETA Train functionality, our aim is to allow the market to become accustomed to the input of valid train numbers. This is why train numbers will be validated from 20 november. If the train number is incorrect, the rotation will be rejected. If for some reason the train number is unknown, there is an option for the rotation to be created using train number 70.000.
Rotation with two visits to the same terminal reported as a single train journey
It was recently made possible for a train journey stopping at the same terminal twice to be reported as a single train journey in HCN Rail. Previously, this required creating two separate train journeys.
It is now possible to report a loop as a single train journey, as shown below:
| AB/12-BA/34 ECT Delta | Friday |
| AB/12-BA/34 EMX | Saturday |
| AB/12-BA/34 APMT2 | Saturday |
| AB/12-BA/34 RWG | Saturday |
| AB/56-BA/56 ECT Delta | Sunday |
Please click here to see which steps you have to take to report a loop as shown in the example above as a single train journey using the HCN RAIL web screens.
If you would like to implement the above change in your TMS, please contact your software provider and have the following fields added within the Create visit endpoint: visitData.dischargeNumber and visitData.loadingNumber.