Development issue: Different ISO type containers between manifest and terminal

Scenario:

• Shipping line or agent registers a container type ‘2210’ on the import manifest
• The shipping line or agent sends a release, the chain is set up and the Inland Operator automatically receives a ‘status request’ for the terminal.
• The terminal registers container type ‘2200’ upon unloading
• The Inland Operator makes a preliminary notification of the ‘status request’ to the terminal, which is rejected due to a different container type.
  • The Inland Operator can change these, but not all terminals accept updates and a new pre-notification is required.
  • The Inland Operator creates a new pre-notification with an adjusted container type ‘2200’, but this is immediately exceeded with ‘2210’ after pre-notification as long as the manifest has not been updated.

Roles:

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

Services:

• MLI
• MCA

Result:

• Pre-notification is rejected.
• 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.

Workaround:

• The Inland Operator must withdraw its pre-notification and resend it after the manifest has been updated if the terminal in question does not accept updates on a pre-notification.
• All parties wait until the manifest has been updated by the shipping line or agent.
• The Inland Operator can submit a new pre-notification, or update an existing one (if possible), with the modified container type.

Planning solution:

• This scenario already existed in port logistics before the introduction of the Secure Chain. Portbase and the Secure Chain are in discussions with all affiliated parties to develop a technical solution for this. Q4 2024.