Automation of IGM submissions: prescribed floppy-based ICES format enforces structured Vessel, Cargo and Container messaging and acknowledgements. The notice mandates submission of IGM messages to ICES via prescribed floppy file format with a three-part structure-Vessel, Cargo and Container-using defined field delimiters and a naming convention; files are validated by the Message Exchange Server, populated into the database only on acceptable format, and Customs issues .ack or .nak acknowledgements. It prescribes message types (prior, post-arrival, final, supplementary, amendment, deletion), mandatory fields, restrictions on amendment of key vessel parameters, procedural rules for line numbering, empty-container handling, and container-number amendment by delete-and-refile.
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.
Automation of IGM submissions: prescribed floppy-based ICES format enforces structured Vessel, Cargo and Container messaging and acknowledgements.
The notice mandates submission of IGM messages to ICES via prescribed floppy file format with a three-part structure-Vessel, Cargo and Container-using defined field delimiters and a naming convention; files are validated by the Message Exchange Server, populated into the database only on acceptable format, and Customs issues .ack or .nak acknowledgements. It prescribes message types (prior, post-arrival, final, supplementary, amendment, deletion), mandatory fields, restrictions on amendment of key vessel parameters, procedural rules for line numbering, empty-container handling, and container-number amendment by delete-and-refile.
Full Summary is available for active users!
Note: It is a system-generated summary and is for quick reference only.
TaxTMI 
of 
Join Channel
TaxTMI 
