Home>ISO Standards>BS ISO 28005-1:2013 pdf free

BS ISO 28005-1:2013 pdf free

BS ISO 28005-1:2013 pdf free.Security management systems for the supply chain一 Electronic port clearance (EPC)
With the following exception, all message exchanges between the ship (or agent) and the SW relating to one specific port call shall be identified by a unique journal number for the port call. The journal number is a field in the message header structure. The exception to this rule is that the first clearance request from the ship (or agent) to the SW shall have an empty tag for the journal number if the journal number is unknown to the ship or agent at the time of transmission. The receipt message from the SW, if the receipt accepts the request, will contain the journal number to be used in all subsequent message exchanges.
This ensures that all messages related to one particular port call can be easily and uniquely identified.
NOTE The SW needs to construct a unique journal number for each ship’s port call and embed it in a token string.All messages from the ship to the Sw, which can be processed by the SW, will receive a receipt message from the Sw. The receipt message signifies one of the following two cases.
a) The information and syntax of the message sent from the ship is free of syntax errors and sufficiently complete to be forwarded to some or all authorities involved. The receipt message lists those authorities to which the request message had been forwarded. Upon receipt of the forwarded message, the authorities begin processing the information for the purpose of issuing a request approval or denial through an acknowledgement message. Port clearance approval or denial is sent to the ship once processing is complete. The receipt message also specifies which, if any, authorities do not have enough information to process their approval or denial decision.
b) The message from the ship contained syntax errors, is incomplete, or contains information that cannot be processed by the SW. The message cannot be forwarded to the authorities and cannot cause any further processing. Incomplete request messages to a SW that do not allow for updates shall be ignored. The message needs to be corrected and resent. Examples of information that cannot be processed include excessively long lists of parties that are copied (copy-to parties), an illegal number of message bodies, illegal message codes or similar.
Messages that cannot be processed by the SW parties shall be silently ignored and shall not receive a receipt.BS ISO 28005-1 pdf download.

Related standards