Start with Hinterland Container Notification Rail for Traction Suppliers

In this article, we explain in a few short steps how to use the service Hinterland Container Notification Rail.

Navigating to the service

You can start HCN Rail as follows:

1. Go to iamconnected.eu
2. Click Login and follow the steps to sign in
3. After login, click the PCS tile
4. In My services, under the Rail section, choose the service Hinterland Container Notification

After you have successfully logged in, you can use the shortcut hcn.pcs.portbase.com.

Dashboard Rotations

On the Rotations dashboard, you have 24/7 real-time insight into train rotations and terminal visits submitted by customers. At the top are the planned rotations that have not started yet. Below that are the rotations in operation, the completed ones, and finally the cancelled rotations.

Train detail view

• Click the trip, visit or handlings for more information
• You can use the Handlings tab to view containers on the visit

Train composition functionality

Below you can read which steps you need to follow to download the Train composition after the terminal has completed the operation. After the operation has been completed at the terminal, the buttons Download train composition (after operations) and Download realised train composition will appear. If these buttons do not become visible after the visit has been completed, please contact the terminal and ask whether they can manually complete the visit in the HCN Rail web screens. Use the contact details below for this.

• APMII: mvii.datacenter@apmterminals.com
• RWG: operations@rwg.nl

Download train composition (after operations)

This file shows the planned outbound Train composition, including any deviations in the remarks. In the Operational Remarks (Slot) and Operational Remarks (Wagon) columns, Planned load/discharge did not occur) or Unplanned load/discharge occured) indicates whether deviations from the plan have occurred at slot/wagon level. The slot position is not always provided by the terminal in the discharge/load confirmation. If this is the case, the unplanned loads/discharges are listed in the Operational Remarks (Wagon) column, where they are by default stated on the wagon at slot position 1.

Download realised train composition

This file shows the actual Train composition after the terminal has completed the operation. Here too, if no slot position is returned by the terminal, the container is by default stated at slot position 1 of the wagon on which the container has been loaded.

Visit status

On the left side of the screen, for each visit, the status of the visit is shown.

• The small aeroplane indicates that the request has been sent.
• A green check mark means that the visit has been accepted.
• A red cross indicates that the terminal has rejected the visit.

The visit can be changed and resubmitted. In the case of a rejected visit, the terminal will include a remark.

In the screen you can also see how the requested visit relates to the slots. In the overview below:

• ECT Delta visit has been submitted and matches the slot
• APMIITEST visit has a different ETD compared to the slot
• RWG visit has a different number of discharge compared to the slot
• The EUROMAX visit is an ad hoc visit; in other words, it has no slot

Rotation and visit level

Rotation level

• At rotation level, the number of containers to discharge and/or load is shown
• If there are containers that need attention, a red triangle with an exclamation mark appears with the number of containers

You can track the progress in the following ways:

• For rotations that are Expected: number pre-notified by operator / number agreed in slot
• For rotations that are In operation: number loaded (discharged) / number pre-notified

Visit level

• By clicking the visit, the terminal visits within the rotation are shown
• At visit level, the number of containers to discharge and/or load is also shown. The red triangle with an exclamation mark indicates which containers need attention. For progress, see the explanation at rotation level
• By opening the visit, the containers that require attention are shown at the top of the list by default

Container status

The following statuses are shown per container (green = OK, red = action required)

Container drop-off

• Padlock icon = block
• Document icon = customs document known at the terminal
• Clock icon = cargo opening started at the terminal
• Key icon = acceptance reference known at the terminal

Container pick-up

• Padlock icon = block
• Document icon = customs document known at the terminal
• Square with check mark = container available at the terminal
• Euro icon = commercial release known at the terminal

ETA Train functionality

The ETA Train functionality is split into two parts:

1. Insight into the location of the train in the hinterland.
2. Insight into the train’s arrival and departure times and the progress of operations at the deep-sea terminals in the Port of Rotterdam.

ETA Train in the hinterland

If you open a rotation to which you have been assigned as a traction supplier, the deep-sea terminals with which the rail operator has made a visit appointment via HCN Rail will appear.

To retrieve the location of the train in the hinterland, the rail operator must share the incoming and/or outgoing train number for the rotation to which you have been assigned, as well as the first departure date and/or outgoing first departure date. If these details are not provided correctly, no match can be made with the train location data from the hinterland, which is supplied by an external party.

From the moment the details have been entered correctly, the ETA Train data is retrieved for the remaining timetable points that the train will pass on its way to the Port of Rotterdam and/or from the Port of Rotterdam back into the hinterland. These points—and therefore the data for each point—only become visible once the train has passed them. By default, these are the departure point in the hinterland, the Dutch border crossing, Barendrecht Vork, and the freight yards at the terminals.

The ETA Train data cannot be retrieved retroactively. This means that if the details are only provided correctly from Barendrecht Vork onwards, the ETA Train information for the departure point in the hinterland and for the Dutch border crossing can no longer be retrieved.

Once the train has passed a timetable point, that timetable point becomes visible in the rotation overview, showing the actual time at which the train passed the point and, in yellow, any delay. This delay is based on the difference between the actual time the train passed the timetable point and the planned time as known in ProRail’s planning.

ETA Train in the Port of Rotterdam

This part of the functionality shows, per pre-notified visit, the arrival and departure times and the progress of operations, and therefore includes the fields below. All these fields can be found on the terminal visit in HCN Rail and are visible to all parties involved in the visit.

1. Estimated time of arrival (ETA)
   • Rail operator: provides the ETA when creating a visit.
   • Terminal & traction supplier: can update the ETA.
   • Under the ETA, you can expand History to see which party provided which ETA.
2. Arrival/departure delay reason
   • Traction supplier: can provide the reason for a train delay.
   • This allows the terminal and the rail operator to better estimate the expected duration and impact of the delay.
3. Actual time of arrival (ATA)
   • Rail operator & terminal & traction supplier: can provide the ATA and update earlier ATA’s (shared by others).
4. Planned start of operations
   • Terminal: can provide and update the expected time of the loading/discharging of the first container until the first CODECO is received.
5. Actual start of operations
   • The actual start of operations is filled automatically when the first discharge/load CODECO for the visit is received in HCN Rail. Once the actual start of operations is known, the planned start of operations is overwritten.
6. Planned finish of operations
   • Terminal: can provide and update the expected time of the loading/discharging of the last container until the last CODECO is received.
7. Actual finish of operations
   • The actual finish of operations is filled automatically when the last discharge/load CODECO for the visit is received in HCN Rail. Once the actual finish of operations is known, the planned finish of operations is overwritten.
8. Estimated time of departure (ETD)
   • Rail operator: provides the ETD when creating a visit.
   • Terminal & traction supplier: can update the ETD.
   • Under the ETD, you can expand History to see which party provided which ETD.
9. Actual time of departure (ATD)
   • Rail operator & terminal & traction supplier: can provide the ATD and update earlier ATD’s (shared by others).

Railwise

At the request of the Rail Connected programme, Portbase has developed a dashboard—called RailWise—that provides insight into the efficiency, capacity and reliability of rail freight transport (containers only). These insights are based on data from HCN Rail and are therefore only available to terminals connected to this service.

How do I get access to RailWise?

In 2025, agreements were made with the participating parties about taking the dashboard. If you are not using the dashboard yet, but would like to do so for the coming year, please let us know before 16 October by contacting our Sales department.

How do I navigate to RailWise?

You navigate to the dashboard by clicking the RailWise tab at the top of the screen in HCN Rail. The dashboard is available on weekdays from 08:00 to 18:00.

Which metrics does RailWise show?

The dashboard is made up of multiple tabs with different metrics, see below.

3.1 Tab KPI’s

This tab shows the metrics below. These metrics are based on the underlying data of the charts on the other tabs. Your KPI’s shows the metrics based on your own data and Market KPI’s shows the market average for the metrics.

See the example below. The screenshot was taken in week 47. The large numbers show the values for the past week (week 46). The smaller values underneath show the figures for the week before (week 45). In the background, you see a grey graph showing the development of these metrics over the past period.

Example chart: number of voyage omits.

1. Number of voyage omits
2. Average number of handlings per hour
3. Average operation time
4. Average call size
5. Average adjusted call size

3.2 Tab Turnaround port

The metrics on the Turnaround port tab provide insight into how many rotations are still changed/cancelled after the planning is definitively fixed in the Spoorboekje in HCN (and therefore not at ProRail!) on Thursday at 23:59.

1. Percentage of cancelled and changed voyages per week market average
2. Number of cancelled and changed voyages per week

3.3 Tab Terminal

The metrics on the Terminal tab provide insight into how efficiently and predictably operational handling at the terminal proceeds.

1. Operation time: percentage of visits with deviation (proforma vs actual) incl. market average
2. Terminal efficiency: average handlings per hour incl. market average

3.4 Tab Call size

The metrics on the Call size tab provide insight into deviations in the call size.

1. Call size: proforma vs replanned vs actual number of equipments
2. Number of calls with deviation proforma vs actual
3. Number of calls with deviation proforma vs replanned

3.5 Tab definitions

This tab contains definitions and explanations of the metrics, KPI’s and terms used in the dashboard. Consult this tab to interpret the figures correctly.

How can I filter the metrics?

The filter options enable you to search your data in a targeted way. It is possible to apply the filters below within the dashboard. The filters may differ per tab.

1. ETA: filter your trips and visits by a specific time period.
2. Rail operator: this filter is only relevant for traction suppliers and terminals and enables them to search specifically for the trips and visits of one or more specific rail operators. As a traction supplier/terminal, you do not see all trips and visits of that rail operator per rail operator, but only the trips and visits that were driven by you for that rail operator / at your terminal.
3. Traction supplier: this filter is only relevant for rail operators and terminals and enables them to search specifically for the trips and visits of one or more specific traction suppliers. As a rail operator/terminal, you do not see all trips and visits of that traction supplier per traction supplier, but only the trips and visits that were driven by that traction supplier for you / at your terminal.
4. Terminal: filter your visits by one or more terminal(s). As a rail operator/traction supplier, you do not see all trips and visits at that terminal per terminal, but only your own visits at that terminal.
5. Shuttle name
6. Loading voyage number
7. Discharge voyage number
8. Deviation: filter on positive/negative deviations.

Which data can I view?

Throughout the entire dashboard, each organisation only sees its own data and, for some metrics, also the market average. The Port of Rotterdam Authority does have insight into your data, provided you have given permission for this. The Port of Rotterdam Authority will contact you separately about this. If you have questions about this, you can contact the Port of Rotterdam Authority.

Email notification

Under Configuration, and then Application preferences, you can enter an email address for status changes for visits.