Development issue: Double releases (with and without PIN)

Scenario:

• The shipping line or agent sends out both a PIN code release and a Secure Chain release.
• The shipping line or agent receives a rejection notification on the Secure Chain release from the terminal. Rejection reason ‘Duplicate Error’ because a PIN release has already been registered for this container.
• Portbase has no influence on the PIN code release
• Portbase registers Secure Chain release as the only truth
• The inland operator cannot make a pre-notification due to a different ‘Accept reference’

Rollen:

• Shipping Line / Agent
• Terminal
• Inland Operator(s)

Services:

• Cargo Declaration Import
• Hinterland Container Notification

Result:

• Pre-notification is rejected.
• The shipping line or agent has no insight into container type discrepancies between manifest and terminal, release has no impact on container type. The shipping line or agent must be actively contacted by Release-to party for manifest update.
• Correcting a PIN code release to a Trust Chain release

Workaround:

• The shipping line or agent must resolve the rejection reason and follow up with an appropriate update.
  • The shipping line or agent must remove the PIN code release via the terminal’s web portal.
  • The shipping line or agent must resend the release (update) via Chain of Trust after the release has been processed. Processing the update can take between 20 minutes and 1 hour.
• The inland operator must withdraw its pre-notification and resend it if the terminal in question does not accept updates to a pre-notification.

Planning solution:

• If all releases go through the Secure Chain, this scenario will disappear , mid 2025.