% Response.CharSet="utf-8" %>
This message is available for formal trial for at least six months from the date of approval by UN/ECE/TRADE/WP.4.
Organisations are invited to trial this message. Comments on the results from the trial should be forwarded to their Rapporteur's Team Secretariat as soon as they are available. Based on the results of the trials, a UNSM may be issued.
The segments, composite data elements, data elements and codes for use in the trial of this message are contained in the Draft directory. However, this information may differ from that in the Standard directory (UNTDID), even for material having the same identifying tags.
|SOURCE:||Western European EDIFACT Board, MD2|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction
This message also occurs in the following versions of this standard:|
D93A, D94A, D94B, D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B
This specification provides the definition of the Bayplan/stowage plan occupied and empty locations message (BAPLIE) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
A message to transmit information about equipment and goods on a means of transport, including their location on the means of transport. The message can be exchanged between (liner's) agents, tonnage centers, stevedores and ships masters/operators (see section 1.3 for more details).
This message may be applied for both national and international trade. It is based on universal practice and is not dependent on the type of business or industry.
In the shipping industry the BAPLIE message can be used between partners as indicated below:
ships/liner ============== 1 ============== ships/liner agents =======2===== =====13====== agents | | | | | 3 | | | | | | | | | | I tonnage ==5 ====== | | ======11= tonnage I centre =========|==|=====|===|==6===== centre | | | | | | | | 7 | | | | | 4 | | | | | | | | =============|==|==8==|===|============= | | | | | | | | | | | | | | | | | | | | | | | | | | | | stevedore============|==|==9==|===|======== stevedore
| | | | | | | | | | | | ====10=== ships master/operator ===12===
PORT OF DEPARTURE(PD) NEXT PORT OF CALL(NC)
1) Agent(PD) to agent (NC) 2) Agent(PD) to ships master/operator(PD) 3) Agent(PD) to tonnage centre (PD) 4) Agent(PD) to stevedore (PD) 5) Tonnage centre(PD) to ships master/operator (PD) 6) Tonnage centre(PD) to tonnage centre (NC) 7) Tonnage centre(PD) to stevedore (PD) 8) Stevedore (PD) to tonnage centre (NC) 9) Stevedore (PD) to stevedore (NC) 10) Stevedore (PD) to ships master/operator (PD) 11) Ships master/operator to tonnage centre (NC) 12) Ships master/operator to stevedore (NC) 13) Ships master/operator to agent (NC)
The above gives only one set of communication channels per organisation but in practice there will be a combination of one or more channels per organisation from or to port of departure/next port of call.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type code for the Bayplan/stowage plan occupied and empty locations message is BAPLIE.
Note: Bayplan/stowage plan occupied and empty locations messages conforming to this document must contain the following data in segment UNH, composite S009:
A segment to indicate the beginning of the message and to transmit function, type and number of the message.
A segment to indicate date and time of the preparation of the message.
A group of segments to specify the document or message to which the current message relates, and related date and time.
A segment to identify a reference which applies to the entire message, e.g. reference to previous message.
A segment to indicate date and time relating to the reference.
A segment to identify the liner service operating or responsible for a particular vessel/voyage.
A group of segments identifying the means of transport and related details.
A segment to identify a means of transport and discharge voyage number.
A segment to identify the locations to which the following information applies.
A segment to indicate date and time of events in local time, else the time zone specifier is to be used.
A segment to identify the loading voyage number.
A segment to transmit general information about vessel/voyage.
SG5 A group of segments containing information about the equipment and/or goods and its stowage location onboard a vessel.
A segment to identify locations relevant to the equipment or goods carried.
A segment to identify the number of packages of the goods.
A segment to identify or specify the goods carried.
A segment to transmit goods descriptions, additional equipment details or other relevant free text.
A segment specifying physical weights related to an equipment detail or a goods item detail.
A segment to identify off standard measurements (e.g. overheight, overlength etc.).
A segment to indicate the temperature setting in relation to an equipment detail.
A segment to transmit a temperature range in relation to an equipment detail.
A segment to identify the locations (ports) to which the given information applies.
A segment to give additional information on equipment or goods carried (i.e. equipment expected to be shifted at the next port).
A group of segments containing information about the type of equipment.
A segment to identify a single piece of equipment to which the following information applies. Only transport equipment size/type coded or plain language is used here further to identify the equipment.
A segment to identify details of equipment attached to the main piece of equipment.
A segment to identify the owner/operator of a particular piece of equipment.
A group of segments containing information about dangerous cargo.
A segment to identify dangerous goods related to an equipment detail.
A segment to give additional information concerning dangerous goods.
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
|BGM||Beginning of message|
|GDS||Nature of cargo|
|GID||Goods item details|
|NAD||Name and address|
|TDT||Details of transport|
|├─UNH Message header||×1||(M)|
|├─BGM Beginning of message||×1||(M)|
|├─Segment Group 1||×9||(C)|
|├─NAD Name and address||×3||(C)|
|├─Segment Group 2||×3||(M)|
|│─├─TDT Details of transport||×1||(M)|
|│─├─LOC Place/location identification||×2||(M)|
|│─└─FTX Free text||×1||(C)|
|├─Segment Group 3||×9999||(C)|
|│─├─LOC Place/location identification||×1||(M)|
|│─├─GID Goods item details||×1||(C)|
|│─├─GDS Nature of cargo||×1||(C)|
|│─├─FTX Free text||×9||(C)|
|│─├─RNG Range details||×1||(C)|
|│─├─LOC Place/location identification||×9||(C)|
|│─├─Segment Group 4||×3||(C)|
|│─│─├─EQD Equipment details||×1||(M)|
|│─│─├─EQA Attached equipment||×9||(C)|
|│─│─└─NAD Name and address||×1||(C)|
|│─└─Segment Group 5||×999||(C)|
|│───├─DGS Dangerous goods||×1||(M)|
|│───└─FTX Free text||×1||(C)|
|└─UNT Message trailer||×1||(M)|