Automated transshipment: EDI-based permits enable container movement to hinterland without separate carrier applications, streamlining manifest closure. Automated transshipment treats the SMTP portion of the IGM as the request for moving containers to inland ports/ICD/CFS, removing the need for separate carrier applications. Carriers must indicate the transporter code in the IGM. Transshipment permit data are sent to carrier, transporter, custodian and destination ICES and can be printed. At destination the permit is auto-converted into an IGM; transporters electronically submit a container arrival report which, when matched with the transshipment message, generates a landing certificate transmitted to the gateway port for IGM line closure.
Cases where this provision is explicitly mentioned in the judgment/order text; may not be exhaustive. To view the complete list of cases mentioning this section, Click here.
Provisions expressly mentioned in the judgment/order text.
Automated transshipment: EDI-based permits enable container movement to hinterland without separate carrier applications, streamlining manifest closure.
Automated transshipment treats the SMTP portion of the IGM as the request for moving containers to inland ports/ICD/CFS, removing the need for separate carrier applications. Carriers must indicate the transporter code in the IGM. Transshipment permit data are sent to carrier, transporter, custodian and destination ICES and can be printed. At destination the permit is auto-converted into an IGM; transporters electronically submit a container arrival report which, when matched with the transshipment message, generates a landing certificate transmitted to the gateway port for IGM line closure.
Full Summary is available for active users!
Note: It is a system-generated summary and is for quick reference only.