Return to Stylus Studio EDIFACT home page. Return to Stylus Studio EDIFACT D02A Messages page. Vessel departure message
0. INTRODUCTIONThis specification provides the definition of the Vessel departure message (VESDEP) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport. 1. SCOPE1.1. Functional definitionA message from a stevedore to a liner agent or from a liner agent to a local authority (e.g. port authority) to inform the latter party of the departure of a vessel and giving information on the actual container or cargo operations. This message is part of a total set of container-related messages. These messages serve to facilitate the intermodal handling of containers by streamlining the information exchange. The business scenario for the container messages is clarified in a separate document, called: 'Guide to the scenario of EDIFACT container messages'. 1.2. Field of applicationThe Vessel departure message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry. 1.3. PrinciplesIn the context of the 'Guide to the scenario of EDIFACT container messages' (as referred to at the start of section 1) the following guidelines, rules and functionality apply to this Vessel departure message:
The ordering customer agent is to supplement the unique identification only when several agents are acting on behalf of the same shipping line for the same voyage number.
The transport sub-working group (D4) has developed recommendations for a harmonised implementation of this message through its subgroup ITIGG (International Transport Implementation Guidelines Group). Users implementing the message are strongly advised to apply these recommendations, which may be obtained from the D4 secretariat. 2. REFERENCESSee UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONS3.1. Standard terms and definitionsSee UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION4.1. Segment clarificationThis section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements. 0010 UNH, Message headerA service segment starting and uniquely identifying a message. The message type code for the Vessel departure message is VESDEP. Note: Vessel departure messages conforming to this document must contain the following data in segment UNH, composite S009:
0020 BGM, Beginning of messageA segment to indicate the beginning of a message and to transmit identifying number. 0030 DTM, Date/time/periodA segment to indicate a date and/or time applying to the whole message, such as date and time of document or message issue. 0040 FTX, Free textA segment to specify free format supplementary information: - change information - additional remarks 0050 Segment Group 1: RFF-DTMA group of segments to specify a reference relating to the whole message, and its date and/or time. 0060 RFF, ReferenceA segment to provide a reference relating to the whole message, such as: - reference to previous message 0070 DTM, Date/time/periodA segment to indicate date and/or time related to the reference. 0080 Segment Group 2: NAD-SG3A group of segments to identify a party and related contacts. 0090 NAD, Name and addressA segment to identify a name and address of a party, such as: - message sender - message recipient - ordering customer/principal - ordering customer agent 0100 Segment Group 3: CTA-COMA group of segments to identify a contact and its communications related to the party. 0110 CTA, Contact informationA segment to identify a person or department for the party, such as: - information contact 0120 COM, Communication contactA segment to identify a communication number of a person or department to whom communication should be directed. 0130 Segment Group 4: TDT-DTM-RFF-SG5-MEAA group of segments to specify details of the departing means of transport. 0140 TDT, Details of transportA segment to identify the transport details of the departing vessel, such as voyage number or an indication of the transport method. 0150 DTM, Date/time/periodA segment to identify a date and time related to the departure of the means of transport. 0160 RFF, ReferenceA segment to identify a relevant reference number, such as: - voyage number 0170 Segment Group 5: LOC-DTMA group of segments to specify a place or port of call of the conveyance. 0180 LOC, Place/location identificationA segment to specify a place or port of call of the means of transport or conveyance, such as: - Maritime Mobile Ship Identifier (MMSI number) 0190 DTM, Date/time/periodA segment to specify date(s) and time(s) related to a location. 0200 MEA, MeasurementsA segment to specify a measurement related to the means of transport, such as: - gross tonnage (of the vessel) 0210 Segment Group 6: QTY-FTXA group of segments to specify total numbers. 0220 QTY, QuantityA segment to specify the actual number of segments in the message and the control reference number of the message. 0230 FTX, Free textA segment to provide supplementary information related to the actual number of operations on equipment. 0240 UNT, Message trailerA service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message. 4.2. Segment index (alphabetical sequence by tag)
4.3. Message structure4.3.1. Segment table
Return to Stylus Studio EDIFACT D02A Messages page. |
Site Map | Privacy Policy | Terms of Use | Trademarks |