Start with Hinterland Container Notification Rail for Traction Suppliers

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

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 Rail, select the Hinterland Container Notification service​

After you have logged in successfully, 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 reported by the customer. At the top are the scheduled rotations that have not started yet. Below that are the rotations in operation, the completed ones and finally the cancelled rotations.

Train details overview​

• Click the journey, 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 completion of the operation by the terminal. After completion of the operation at the terminal, the buttons Download train composition (after operations) and Download realised train composition will appear. If these buttons are not 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.

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

Download train composition (after operations)

This file shows the planned outgoing 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 planning occurred at slot/wagon level. The slot position is not always provided by the terminal in the load/discharge confirmation. If this is the case, the unplanned loads/discharges are stated 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 completion of the operation by the terminal. Here too, if no slot position is fed back by the terminal, the container is by default stated at slot position 1 of the wagon on which the container is loaded.

Status of the visit

On the left side of the screen, each visit shows the status of the visit.

• The 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 event of a rejected visit, the terminal will send a remark.

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

• ECT Delta visit has been reported 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, including the number of containers

You can track 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, read the explanation under rotation level
• By opening the visit, the containers that require attention are shown at the top of the list by default​

Container status​

For each container, the statuses below are shown (green = OK, red = action required)

Container delivery​

• 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 the operation 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 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, it is necessary that the rail operator shares the incoming and/or outgoing train number on 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 supplied by an external party.

From the moment the details are entered correctly, the ETA Train data will be 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 also the data for each point, only become visible once the train has passed them. Standard points 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, the 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 schedule.

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 the operation and therefore includes the fields below. All of 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 helps the terminal and the rail operator 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 ATAs (shared by others).
4. Planned start of operations
   • Terminal: can provide and update the expected moment of the loading/discharge 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 load/discharge 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 moment of the loading/discharge 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 load/discharge 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 ATDs (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 that are connected to this service.

How do I get access to RailWise?

In 2025, agreements were made with the participating parties regarding the purchase of 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 can 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 consists 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 chart 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 being changed/cancelled in HCN (and therefore not at ProRail!) at 23:59 on Thursday after the planning has been definitively recorded in the timetable.

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 operations at the terminal are handled.

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 equipment
2. Number of calls with deviation proforma vs actual
3. Number of calls with deviation proforma vs replanned

3.5 Definitions tab

This tab contains definitions and explanations of the metrics, KPI’s and concepts 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 journeys 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 journeys and visits of one or more rail operators. As a traction supplier/terminal you do not see all journeys and visits of that rail operator per rail operator, but only the journeys and visits that you have operated 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 journeys and visits of one or more traction suppliers. As a rail operator/terminal you do not see all journeys and visits of that traction supplier per traction supplier, but only the journeys and visits operated 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 journeys 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 by positive/negative deviations.

Which data can I view?

Across the entire dashboard, every 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 that you have given permission for this. The Port Authority will contact you separately about this. If you have any questions about this, you can contact the Port of Rotterdam Authority.

Email notification​

Under Configuration, then Application preferences, you can enter an email address for visit status change notifications.​