Portbase has been asked by the Secure Chain to make the import container release process in the Port of Rotterdam safer and more reliable. In various service, an additional authorisation layer is being added. Through this authorisation layer, the different parties in the logistics chain digitally pass on to each other the right to collect a container. In this way, a closed chain is created with authorised parties only.
Before you continue reading, first read the latest status and how the Secure Chain works.
Introduction to roles and service
Within the Secure Chain, we have various roles and rights. In this article we refer to these. In the image below you can see an explanation of the roles.
Portbase supports the Secure Chain within our existing service. The target groups therefore continue to work in their trusted service.
The shipping line/shipping agent can create a release in ships' calls.
Shippers/forwarders choose between Cargo Release Manager or Cargo Controller Import to participate in the Secure Chain.
Inland operators receive a notification in Hinterland Container Notification (HCN) that the container can be collected. The container is reserved for the nominated party.
In this article we go deeper into the supply chains and variants you may encounter within the Secure Chain.
You can only start with the Secure Chain once you have informed all your chain partners; without the final link, you cannot start releasing containers securely.
Different roles and chains
The shipping agent can only release to shippers/forwarders who have linked a shipping line customer code to the shipping agent. You can find how this linking works in Register customer code for the Secure Chain. When goods are released directly to you, you are the "release-to-party" in the chain.
From the perspective of a shipper/forwarder, as an organisation you can fulfil different roles within different chains. This depends on the type of goods or obligations that each chain brings with it. Below is a schematic representation showing you acting as release-to-party or, as a forwarder, in a different role.
Different (Secure Chain) roles
Each role can only see its client and to whom the assignment has been passed on. This keeps the chain transparent.
- Shipping line/shipping agent: Carrier
- This role is unique in the chain.
- Passes the release to the release-to-party and, via Portbase, to the terminal.
- Received release: release-to-party
- This role is unique in the chain.
- Receives the release from the Carrier.
- The roles of release-to-party and cargo director can be combined by 1 party.
- Passes the release on to a cargo director (forwarder) or to an inland operator (inland operator).
- Forwarder: cargo director
- This role can occur multiple times in the chain.
- Receives the release from the Carrier or another cargo director.
- Passes the release on to a cargo director (forwarder) or to an inland operator (inland operator).
- Inland operator: inland operator
- This role can occur multiple times in the chain.
- Receives the release from the Carrier or another cargo director.
- Passes the release on to another inland operator (inland operator) or arranges the pre-notification to the terminal.
- The inland operator can include a charter in their role if they submit the pre-notification to the terminal for this charter.
Different chains
It is even possible that you are active in different chains, with more or fewer chain partners. Below are the types of chains that Portbase can support at the moment. The shipping line determines the start moment when you become active in the Secure Chain, but it is then up to the release-to-party to prepare all chains and all chain parties for this.
In the next step, we continue with activating the Secure Chain.
The role of inland operator and cargo director can be passed on indefinitely.
Identification and verification
In the previous steps, we guided you through the preparations for actually using the Secure Chain within Portbase. To receive a commercial release via the shipping line, you must first register a customer reference number.
To activate this, you need the rights of the main user or user administrator of your organisation; this is managed within your organisation’s IAM account.
The next steps are described in the article Register customer code for the Secure Chain.
Starting the Secure Chain
In consultation with the shipping line, you jointly decide from when releases will be made via the Secure Chain. You can read everything about this process here.
The operational timeline and the timing of steps
We would like to explain more about how the theory can occur in practice. The order in which steps are taken may be as follows:
Certain information is only accessible to parties who are actually permitted to view it, by means of nomination and authorisation.
Would you like to get started right away with the Secure Chain and Cargo Controller Import? Then read the article Starting the Secure Chain in Cargo Controller Import.
Related to