Development issue: Release is rejected by terminal

Scenario:

• A release can be denied by Terminal
• A release period can expire, and after the release deadline is rejected by the terminal.

Roles:

• Shipping Line / Agent
• Terminal

Services:

Result:

• Existing chains with Secure Chain releases remain active. However, the release is no longer valid at the terminal
• The pre-notification in HCN shows a red sphere on commercial release with the message COR
• The release has not been processed by the terminal, the shipping company must take action.

Workaround:

• A release period can expire, and an update can be sent with a new date. The terminal can refuse this update, resulting in a ‘rejection’ message.
  • Shipping company must resolve the rejection reason and follow up with an appropriate update.
• A release has been changed by the shipping company at the terminal via the terminal’s web portal or the previous release has still expired outside Portbase.
  • If the release has expired outside Portbase (PCS), the shipping company must update the PIN code release via the terminal’s web portal.
  • If the release should have taken place via Portbase (PCS), the PIN code release must be revoked at the terminal. Then process a PCS release.
• If the release went through Portbase (PCS), but was subsequently updated in the terminal web portal, the entire release must be revoked.
  • This stops the entire active chain until the release is issued again.
    • A new release disrupts the pre-notification of the Inland Operator at a terminal. This will have to be pre-notified again in accordance with the rules that apply at the terminal in question. Read more about that here.

Planning solution:

• If all releases go through the Secure Chain, this scenario will occur less often. Mid 2025.