Baplie30

7/28/2019 Baplie30

1/88

ITSG

180613/HH:06 (print date/time) GJE

DRAFT

USER MANUAL(IMPLEMENTATION GUIDE)

UN/EDIFACT BAYPLAN MESSAGE

BAPLIE

Version 3.0

D00B

7/28/2019 Baplie30

2/88

Version : 3.0.0/D00BDate : 10/2000Source : SMDG User Group for Shipping Lines and Container Terminals

7/28/2019 Baplie30

3/88

SMDG

Information in this document is subject to change without notice.

The SMDG claims full copyright to this manual and its contents, however,

the manual may be copied and used by anyone, without the consent of SMDG.

It is not allowed to change the contents of this manual!

7/28/2019 Baplie30

4/88

SMDG

USER MANUAL BAPLIE 3.0

CONTENTS

0. INTRODUCTION..............................................................................................................3

1. ADDRESSES.....................................................................................................................4

2. GENERAL..........................................................................................................................5

3. VERSIONS..........................................................................................................................7

4.SEGMENT USAGE............................................................................................................9UNB 9UNH 10BGM 11DTM 12RFF 13NAD 14Group grp1................................................................................................................................15

TDT (grp1)................................................................................................................................15LOC (grp1)................................................................................................................................17DTM (grp1)...............................................................................................................................19RFF (grp1).................................................................................................................................20FTX (grp1)................................................................................................................................21Group grp2................................................................................................................................22LOC (grp2)................................................................................................................................22GID (grp2)................................................................................................................................ .23GDS (grp2)................................................................................................................................24FTX (grp2)................................................................................................................................25MEA (grp2)...............................................................................................................................27DIM (grp2)................................................................................................................................28TMP (grp2)................................................................................................................................29

RNG (grp2)................................................................................................................................30LOC (grp2)................................................................................................................................31RFF (grp2).................................................................................................................................34Group grp3................................................................................................................................35EQD (grp3)................................................................................................................................35EQA (grp3)................................................................................................................................37NAD (grp3)....................................................................................................................... ........38Group grp4................................................................................................................................39DGS (grp4)................................................................................................................................39FTX (grp4)................................................................................................................................42UNT 43UNZ 44

5. SPECIAL USER GUIDELINES AND EXAMPLES.....................................................46

SMDG/102000/BAPLIE 3.0.0/D00B Page : 1

7/28/2019 Baplie30

5/88

SMDG


Breakbulk cargo (B/B)..............................................................................................................46Example # 1 a:...........................................................................................................................47Example # 1 b:...........................................................................................................................48

Example # 1 c:...........................................................................................................................49Example # 1 d:..........................................................................................................................51Example # 1 e:...........................................................................................................................53

6. MESSAGE STRUCTURE DIAGRAM..........................................................................55

7. SEGMENT DIRECTORY (D.00B).................................................................................57

8. SMDG EDI-ELECTRONIC DATA INTERCHANGE UNDERSTANDING.............72


7/28/2019 Baplie30

6/88

SMDG


0. INTRODUCTION

The instructions are valid for the "UN/EDIFACT UNITED NATIONS STANDARD MESSAGE(UNSM) BAYPLAN/STOWAGEPLAN OCCUPIED AND EMPTY LOCATIONS MESSAGE"(BAPLIE), as designed by the SMDG (User Group for Shipping Lines and Container Terminals).

The instructions in this manual are valid for Full Container Vessels, Container Feeder Vessels and Rollon/Roll off (Ro/Ro) Vessels.

This manual is intended for use by ship owners, tonnage centers, terminal operators, shipping lines,vessels, etc.

This "User Manual" (or "Implementation Guide") version 3.0 was developed in 2000 by the SMDGUserGroup for Shipping Lines and Container Terminals.

The SMDG is a "Worldwide User Group" under the auspices of the Western European Edifact Board(WEEB).

The SMDG claims full copyright to this manual and its contents, however, the manual may be copied andused by anyone, without the consent of the SMDG.

It is not allowed to change the contents of this manual!


7/28/2019 Baplie30

7/88

SMDG


1. ADDRESSES

Any remarks, comments or questions can be addressed to one of the following addresses:

SMDG Secretariatc/o ECTP.O.Box 7400

3000 HK RotterdamThe NetherlandsPhone: 31-10-4916075Fax: 31-10-4916865Email: [email protected]: www.smdg.org

or to any active member of the SMDG. See the member pages on our website for email addresses.

Any remarks or questions can also be placed on our forum: go to www.smdg.organd select forum.

mailto:[email protected]://www.smdg.org/http://www.smdg.org/http://www.smdg.org/mailto:[email protected]://www.smdg.org/http://www.smdg.org/

7/28/2019 Baplie30

8/88

SMDG


2. GENERAL

The EDIFACT Bayplan "BAPLIE" will be used to transmit information about ALL occupied places

onboard of a vessel to interested parties like the ship owner and the terminal operator in the next port ofcall. Although the message is also suitable to transmit information about empty places, this feature willnot be used.

In general only complete messages "BAPLIE" have to be transmitted, whereas only occupied stowagelocations, either by equipment or special cargo (breakbulk), should be mentioned. Alternatively it may beagreed between EDI-partners to transmit only details about containers handled in that port ('exports' only)to the central planning office, where the master bayplan details can be updated accordingly.

The Principle

The message will be transmitted to the terminal operator in the next port of call, who will then be able toextract the information relevant to his operation from the message.

Subsequently the information about equipment discharged from the vessel on his terminal will beremoved, information about equipment loaded at his terminal will be inserted and the location ofequipment shifted at his terminal will be changed.

Upon sailing of the vessel he will then transmit the updated bayplan-message to the ship owner, tonnagecenter and/or the terminal operator in the next port of call, as per the instructions of the ship owner. Themessage can be transmitted to the vessel (i.e. via modem or by floppy disk) eliminating the use of the

paper "master" bayplan.

In case complete 'master' bayplans are being transmitted the receiving party should ensure that all data forthe so-called 'remains on board' cargo remains intact for re-transmission to the next port.

Conventions

In this document a data element will be identified by the lowercase letter "e" followed by its elementnumber (example: e8053). A data element within a composite will be identified by the lowercase letter "c"followed by the composite number followed by a full stop "." followed by the lowercase letter "e" followed

by the element number (example: c237.e8260).

Immediately below the segment tags and data element identification the usage of same will be mentionedas follows:

'M' = mandatory The segment or data element is mandatory and must be given.

'R' = required The segment or data element is conditional but MUST be used anyway.

'D' = dependent The segment or data element is conditional and its use depends on somecondition. This condition must be clarified in the description.

'A' = recommended The segment or data element is conditional and its use is recommended.

'O' = optional The segment or data element is conditional and its use is optional at thediscretion of the sender.

'X' = not used The segment must not be used.

Next to the usage indicator the official format of the field will be given, i.e. a4 or an..15. The descriptionmay further limit the format of the field, for example a field with a format an..17 may be limited to an12

by its description.


7/28/2019 Baplie30

9/88

SMDG


If composites or data-elements are repeated within a segment, respectively a composite, the occurrences ofthe composites or data-elements can be indicated by its sequence number within the segment or composite

between brackets, e.g. "(1)" being the first occurrence of the composite or data-element within thesegment. If its occurrence within the segment or composite is of no relevance then the sequence numberwill not be mentioned. If the sequence numbers are mentioned, but not all of them (e.g. only 2 out of 5occurrences are described), then the remaining occurrences may NOT be used, unless agreed otherwise

between partners.

Data elements within the segments that are not mentioned here will not be used, resp. should not containimportant information, since they will probably not be seen by the recipient, unless agreed otherwise.

SMDG recommends to use only data elements, qualifiers and codes described in this manual. If partnersagree to use additional data elements, qualifiers and codes, not described in this manual, then specific anddetailed agreement about those data elements, qualifiers and codes should be made!

Optional data elements may be omitted, unless specifically made compulsory by this manual (Indicator"R" = required), or unless agreed otherwise between partners.

In no case neither mandatory segments according to the Bayplan Message Documentation "BAPLIE" normandatory composites or data elements according to the relevant Segment Directory may be omitted.

In case of Consortia vessels, the codes required by the vessel operator should be used, when sending(copies of) the BAPLIE message to the various lines.


7/28/2019 Baplie30

10/88

SMDG


3. VERSIONS

Data elements, composites and segments of the UN/Edifact directory D00B (July 2000) are used in this

manual.

Codes and qualifiers used, are according to UN/EDIFACT Directory D00B Code List.

In some occasions, however, the required code or qualifier could not be found in the code list. In suchcases a temporary code was assigned, awaiting the final code allocation from the UN/Edifact Board Codecommission.

This version 3.0 is based upon the previous version 2.0 with some adjustments, corrections andimprovements, as proposed by the members of SMDG.


7/28/2019 Baplie30

11/88

SMDG


This page is left blank intentionally.


7/28/2019 Baplie30

12/88

SMDG


4. SEGMENT USAGE

UNB(M1)

+s001.e0001

:

(M n1)

+

s002.e0004

+

s003.e0010

+

s004.e0017

:

s004.e0019

+

e0020

+++++e0032

INTERCHANGE HEADER

Syntax Identifier: Always "UNOA", indicating the useof level "A" character set.

Syntax Version Number: Always "2".

Sender Identification: Name code of the sender of the

interchange (message). To be agreed between partners.

Recipient Identification: Name code of the recipient of theinterchange (message). To be agreed between partners.

Date of preparation: Preparation date of the interchange(message).

Time of preparation: Preparation time of the interchange(message).

Interchange control reference: A reference allocated by thesender, uniquely identifying an interchange. This reference mustalso be transmitted in the Interchange Trailer segment UNZ.

Communications Agreement Id: A code identifying the shippingline of the vessel (BIC, SCAC or mutually agreed).

N.B. This code enables proper routing of the message by therecipient, even if the sender is not the shipping line (e.g.container terminal in the previous port).


7/28/2019 Baplie30

13/88

SMDG


UNH(M1)+

e0062

+

s009.e0065

:

s009.e0052

:

s009.e0054

:

s009.e0051

:

s009.e0057

'

MESSAGE HEADER

Message reference number: A reference allocated by the

sender, uniquely identifying a message. This reference must also be transmitted in theMessage Trailer segment UNT.

Message Type Identifier: The name of the UNSM or standardEDIFACT message. In this case always "BAPLIE".

Message Type Version Number: The version number of themessage. See EDIFACT documentation. At this moment the version is "D".

Message Type Release Number: The release number of themessage. See EDIFACT documentation. At this moment the release number is "95B".

Controlling Agency: The code of the controlling agency. Forthis message the controlling agency is "UN".

Association Assigned Code: The applicable SMDG User Manualversion number. For this manual always: "SMDG30". This will enable the recipient ofthe message to translate the message correctly, even if older versions are still in use.


7/28/2019 Baplie30

14/88

SMDG



BGM(M1)

++

c.106.e1004

+

e1225

'

BEGINNING OF MESSAGE

Document identifier: Reference allocated by the senderindividually, taken from the application.

Message Function Code: Code indicating the function of themessage. Acceptable codes are:

"2" = Add."3" = Delete."4" = Change."5" = Replace."9" = Original."22" = Final.

Add to previous message.Delete from previous message.Message with changes on previous message.Message replacing a previous one.First or basic message.The final message in a series of BAPLIE messages.

In principle only original messages (code "9") are allowed. The other codes may beused after prior agreement between sender and recipient.

7/28/2019 Baplie30

15/88

SMDG


DTM(M1)

+

c507.e2005

:

c507.e2380(R an..35)

:

c507.e2379

(R an..3)

'

DATE/TIME/PERIOD

Date or time or period function code qualifier:Code "137" (Document/Message Date/Time)

Date or time or period value:Date or date/time of compiling the message.

Date or time or period format code: Allowed codes:"101" = YYMMDD"201" = YYMMDDHHMM"301" = YYMMDDHHMMZZZ ("ZZZ" = Time zone, e.g. "GMT" or other)


7/28/2019 Baplie30

16/88

SMDG


RFF(X)

REFERENCE

This segment not to be used.


7/28/2019 Baplie30

17/88

SMDG



NAD(X)

NAME AND ADDRESS

This segment is not to be used.

7/28/2019 Baplie30

18/88

SMDG


Group grp1TDT - LOC - DTM - RFF - FTX.

(M1)


TDT (grp1)(M1)+

e8051(M an..3)+

e8028(R an..17)

+++

c040.e3127(R an..17)

:

c040.e1131(R an..3)

:

c040.e3055"20"

+++

c222.e8213(R an..9)

:

DETAILS OF TRANSPORT (grp1)

Transport Stage Code Qualifier: Code "20" (Main Carriage)

Means of Transport Journey Identifier:Discharge voyage number as assigned by the Operating Carrier or his agent. Thetrade route could be included in this voyage number, if required.

Carrier Identification: Carrier name, coded. Codes to beagreed or standard carrier alpha code (SCAC).

Code List Identification Code: Code "172" (Carrier Code)

Code list responsible agency code. Allowed codes:= BIC (Bureau International des Containeurs)"166" = US National Motor Freight Classification Association (SCAC)"ZZZ" = Mutually defined.

Transport means identification name identifier.Vessel code:1. Call sign (recommended)2. Lloyd's Code3. Mutually agreed vessel code

7/28/2019 Baplie30

19/88

SMDG



TDT

c222.e1131(R an..17)

:

c222.e3055(R an..3)

:

c222.e8212(R an..35)

:

c222.e8453(O an.. 3)

'

(Continued)

Code List Identification Code:Allowed codes:"103" = Call Sign"146" = Means of Transport Identification = Lloyd's Code"ZZZ" = Mutually defined

Code list responsible agency code. Allowed codes:

"11" = Lloyd's register of shipping. Only to be used when Lloyd's Code isused for vessel/barge identification (Code "146" in c222.e1131)."ZZZ" = Mutually defined. To be used in all other cases.

Transport means identification name: Vessel name, if required.

Transport means nationality code: Coded according toUN-countrycode (ISO 3166).

7/28/2019 Baplie30

20/88

SMDG


LOC(grp1)(M9)

+

e3227

+

c517.e3225

:

c517.e1131(R an..17)

:

c517.e3055

+

c519.e3223(O an..25)

:

c519.e1131

:

(O an..3)

+

PLACE/LOCATION IDENTIFICATION (grp1)

Location function code qualifier: Allowed qualifiers:"5" = Place of Departure"61" = Next port of call

Location name code: Location code of the actualplace of departure (normally the sender of the message). If possible, UN-Locodes of5 characters according to UN recommendation no.16. must be used.

Code list identification code. Allowed code:"139" = Port.

Code list responsible agency code. Allowed codes:"112" = US, US Census Bureau, Schedule D for U S locations, Schedule K forforeign port locations."6" = UN/ECE - United Nations - Economic Commission for Europe. (UN-Locodes).

First related location name code. The ISO countrycode.

Code list identification code. Allowed code:"162" = Country.

Code list responsible agency code. Allowed code:"5" = ISO


7/28/2019 Baplie30

21/88

SMDG


LOC

c553.e3233

:

c553.e1131

'

(Continued)

Second related location name code. The state or

province code, postal abbreviations.

Code list identification code. Allowed code:"163" = Country sub-entity; state or province.

N.B. If locodes other than UN-locodes are used the sender must verify with the recipient of the message ifother than UN-locodes are acceptable. Composites c519 and c553 are only relevant if no UN-locodes areused.


7/28/2019 Baplie30

22/88

SMDG


DTM(grp1)(M99)

+

c507.e2005

:

c507.e2380

:

c507.e2379(R an..3)

'

DATE/TIME/PERIOD (grp1)

Date or time or period function code qualifier: Allowed qualifiers:"178" = actual date/time of arrival at senders port"132" = estimated date or date/time of arrival at the next port of call"133" = estimated date or date/time of departure at senders port"136" = actual date/time of departure at senders port

Date or time or period value: Date or date/time in local time when Meansof Transport has arrived/departed or is expected to depart at the senders port or isexpected to arrive at the next port of call.

Date or time or period format code. Allowed codes:"101" = YYMMDD"201" = YYMMDDHHMM"301" = YYMMDDHHMMZZZ ("ZZZ" = Time zone, e.g. "GMT" or other)


7/28/2019 Baplie30

23/88

SMDG


RFF(grp1)(C1)

+

c506.e1153

:

c506.e1154(R an..70)

'

REFERENCE (grp1)

Reference code qualifier: Code "VON" (Loading Voyage number, ifdifferent from the voyage number in the TDT-segment, assigned by the OperatingCarrier or his agent to the voyage of the vessel).

Reference identifier: The Loading voyage number.


7/28/2019 Baplie30

24/88

SMDG



FTX(grp1)(X)

FREE TEXT (grp1)

At this moment there is no use for this segment.

7/28/2019 Baplie30

25/88

SMDG


Group grp2

(C9999) LOC - GID - GDS - FTX - MEA - DIM - TMP - RNG - LOC -RFF - grp3 - grp4

LOC(grp2)(M1)

+

e3227(M an..3)

+

c517.e3225

::

c517.e3055(R an..3)

'


Location function code qualifier:Qualifier: "147" (Stowage Cell)

Location name code: The actual location of the equipment or cargo on the vessel.The following formats are allowed:

1. ISO-format2. Ro/Ro-format3. Other non-ISO-format (to be agreed between partners)

1. ISO-format:Bay/Row/Tier (BBBRRTT). If Bay number is less than 3 characters it must befilled with leading zeroes, e.g. "0340210".

2. Ro/Ro-format:Deck/Bay/Row/Tier (DDBBBRRTT).

Code List Responsible Agency code: To indicate which format is used.Valid codes are:"5" (ISO-format)"87" (Ro/Ro-format, assigned by the Carrier)"ZZZ" (non-ISO-format, mutually defined).

Remarks:

1. This LOC-segment is M1 and should not allow duplicate cell-locations for normal heightcontainers except following cases.

2. In case flat rack containers stowed in one stowage location and not bundled, they should betransmitted as individual units in the same stowage location.

In case of bundles of flat rack containers in one stowage location the number of the leading-unitshould be given in the EQD-segment and the other numbers in the EQA-segment. In such caseMEA-segment must show the total weight of containers. Otherwise you may duplicate LOC-segment with comment showing bundled cargo in FTX segment (grp2).

3. In case two half height containers stowed in one stowage location, Group 2 should betransmitted twice with the same stowage location.


7/28/2019 Baplie30

26/88

SMDG


GID(grp2)(C1)

++

c213.e7224(O n..8)

:

c213.e7065

'

GOODS ITEM DETAILS (grp2)

Package quantity. The number of packages of non-containerized cargo. If thecargo is Ro/Ro then the number "1" is used.

Package type description code. Package type for non-containerized cargo.


7/28/2019 Baplie30

27/88

SMDG



GDS (grp2)(C9)

+

c703.e7085(M an..3)

'

NATURE OF CARGO (grp2)

Cargo type classification code. Codes to be agreed between partners.

If this data is required, we recommend the use of the Harmonized CommodityDescription and Coding System code list of cargo nature (HS).This code list is as follows:"01" = Live animal"06" = Live plant"09" = Coffee

"10" = Wheat"12" = Hay"22" = Malt"24" = Tobacco"41" = Hide"44" = Timber pack"48" = Waste paper"49" = News print"52" = Cotton"68" = Stone"72" = Iron scrapFurther details can be given in the following FTX-segment, if required.

7/28/2019 Baplie30

28/88

SMDG


FTX (grp2)(C9)

+

e4451

+++

c108.e4440

'

FREE TEXT (grp2)

Text Subject Code Qualifier: Allowed qualifiers:"AAA" = Description of Goods"HAN" = Handling Instructions"CLR" = Container Loading Remarks"SIN" = Special instructions"AAI" = General information"ZZZ" = Mutually defined use

Free Text Value: Description/Instructions/Remarks in plain languageor coded, for specific cargo/equipment. Codes, etc. to be agreed between partners.One element with maximum field length 20 characters, unless agreed otherwise.


7/28/2019 Baplie30

29/88

SMDG


FTX (grp2) (Continued)

N.B. This segment is not generally machine processable. Use of this segment must be agreedbetween partners!

This segment can be used for the following:

a. "AAA": Description of goods, plain language or codes, as agreed between partners. Maximum 20characters.

b. "SIN": Additional information or instructions regarding special cargoes, equipment or breakbulkshipments. The following code list can be agreed between partners:

1. General:"SWS" = Sandwich Stow (Break bulk)

2. For ventilated containers:

"CLS" = Close "QUA" = 1/4 open"HLF" = 2/4 open "THR" = 3/4 open"FLL" = full open"050" = volume of flowing 050m3/hour

c. "HAN": For handling instructions the following codes are recommended:"AB" = Away from boiler (eng.room) "OD" = On deck stowage"TS" = Top stowage "UD" = Under deck "UT" = Under deck top "UW" = Under waterline"OT" = On deck top "EO" = Except on deck top"OP" = On deck protected "KC" = Keep cool"AL" = Away from living quarters "BC" = Block stowage

"AF" = Away from foodstuffs "NO" = Not over stow"FC" = Floating Crane handling "OS" = Over side delivery"OQ" = Over side delivery by Quay crane"SM" = Shore side delivery by Mobile crane

d. "CLR": Container loading remarks: the following codes are recommended:"BD" = Bundled "DM" = Damaged mt"SW" = Sweeper "ER" = Escort required"DR" = Dry reefer "HT" = Hangertainer "DO" = Doors open "MB" = Mailbox"ND" = Door removed


7/28/2019 Baplie30

30/88

SMDG


MEA (grp2)(M9)

+

e6311(M an..3)

++

c174.e6411(M an..3)

:

c174.e6314

'

MEASUREMENTS (grp2)

Measurement Purpose Code Qualifier: Allowed qualifiers:"WT" (gross weight)

Measure Unit Code: Allowed codes:"KGM" = kilogram = preferred"LBR" = pounds

Measurement Value: The actual tare weight of the equipmentplus its eventual contents in kilograms or pounds, as qualified (no decimals).


7/28/2019 Baplie30

31/88

SMDG



DIM (grp2)(C9)

+

e6145

+

c211.e6411(M an..3)

:

c211.e6168

:

(D n..15)

:

(D n..15)

'

DIMENSIONS (grp2)

Dimension Type Code Qualifier: Allowed qualifiers are:Code "1" = Gross dimensions (break bulk)Code "5" = Off-standard dims. (over length front)Code "6" = Off-standard dims. (over length back)Code "7" = Off-standard dims. (over width right)Code "8" = Off-standard dims. (over width left)Code "9" = Off-standard dims. (over height)Code "10" = external equipment dimensions (Non-ISO equipment)Basically allowed qualifier "1" for break bulk cargo and from "5" to "9" for odd-sized-cargo. However allowed from "5" to "9" for break bulk cargo as additionalinformation, if required.

Measurement Unit Code: Allowed codes:"CMT" = Centimeters = preferred"INH" = Inches

Length Dimension Value. Break bulk length or over length forcontainers, as qualified.

Width Dimension Value: Break bulk width or over width for containers,as qualified.

Height Dimension Value: Break bulk height or over height forcontainers, as qualified.

N.B. This segment is only to be transmitted in case break bulk, odd-sized-cargo and off-standard ornon-ISO equipment is involved. In order to identify all relevant information, this segment may

be repeated conditionally up to 9 times.

7/28/2019 Baplie30

32/88

SMDG


TMP (grp2)(C1)

+

(M an..3)

+

c239.e6246

:

c239.e6411(R an..3)

'

TEMPERATURE (grp2)

Temperature type code qualifier: Allowed qualifier:"2" = Transport Temperature

Temperature Value: Actual temperature according to ReeferList (no deviation allowed) at which the cargo is to be transported. For fieldformat see remarks below.

Measurement Unit Code: Allowed codes:"CEL" = degrees Celsius = Preferred."FAH" = degrees Fahrenheit

N.B. In spite of the field length of element c239.e6246 (temperature) is only N3 decimal mark andfigure as well as negative values preceded by a sign (-) can be transmitted. Generally numericdata element values shall be regarded as positive unless they are preceded by a minus sign. Thedecimal mark and minus sign shall, however, not be counted as a character of the value whencomputing the maximum field length of a data element. Nevertheless, allowance has to be made

for the character in transmission and reception.Tenth degrees have to be separated by a decimal point from full degrees (e.g. 18.5).Temperatures below zero have to be preceded by a minus sign (e.g. "-18.5", "-02.5", "004","04.5"). The same applies for elements c280.e6162 and c280.6152 in the following RNG-segment.For further explanation please refer to ISO 9735 "EDIFACT Application Level Syntax Rules",

point 10 "Representation of numeric data element values".

Remarks about DRY REEFER:In case of shipment of a so called "dry reefer" (non-running reefer unit, empty or loaded with ordinarycargo) the TMP-segment must NOT be transmitted. The container type (reefer) can be identified in theEQD-segment by its ISO-size-type code. The absence of the TMP-segment indicates that the unit is not

running.


7/28/2019 Baplie30

33/88

SMDG



RNG (grp2)(C1)

+

e6167(M an..3)

+

c280.e6411(M an..3)

:

c280.e6162

:

c280.e6152

'

RANGE DETAILS (grp2)

Range Type Code Qualifier: Allowed qualifier:"4" = Quantity range.

Measurement Unit Code: Allowed codes:"CEL" = degrees Celsius"FAH" = degrees Fahrenheit

Range Minimum Value: Minimum temperature according to Reefer Listat which the cargo is to be transported.

Range Maximum Value: Maximum temperature according to Reefer Listat which the cargo is to be transported.

Remarks:Use of segments TMP and RNG are not depending on each other, i.e. you can transmit either TMP orRNG or both.

7/28/2019 Baplie30

34/88

SMDG


LOC (grp2)(C9)

+

e3227(M an..3)

+

c517.e3225

:

c517.e1131(O an..17)

:

c517.e3055

+


Location Function Code Qualifier: Allowed qualifiers:"9" = Place/Port of Loading"11" = Place/Port of discharge"13" = Transhipment port/Place of transhipment"64" = 1st optional port of discharge"68" = 2nd optional port of discharge"70" = 3rd optional port of discharge"76" = Original port of loading"83" = Place of delivery (to be used as final destination or double stack train"97" = Optional place/port of discharge. To be used if actual port of discharge isundefined, i.e. "XXOPT".

"152" = Next port of discharge

Location name code: Name code of the place/port, asqualified. Allowed code lists: UN-Locode or US-Census codes.Sample codes: JPTYO = Tokyo

USLAX = Los AngelesUSOAK = OaklandUSSEA = SeattleUSCHI = Chicago

For optional port of discharge: "XXOPT" (Qualifier e3227: "97").

Code list identification code. Allowed codes:"139" = Port.

Code list responsible agency code. Allowed codes:"112" = US, US Census Bureau, Schedule D for U S locations, Schedule K for foreign"6" = UN/ECE - United Nations - Economic Commission for Europe. (UN-Locodes)."ZZZ" = Optional ports.


7/28/2019 Baplie30

35/88

SMDG


LOC (grp2)

c519.e3223(O an..25)

:

c519.e1131

:

c519.e3055(O an..3)

+

c553.e3233

:

c553.e1131

'

(Continued)

First related location name code. The ISO country code.

Code list identification code. Allowed code:"162" = Country.

Code list responsible agency code. Allowed codes:"5" = ISO

Second related location name code. The state or province code, postal abbreviations.

Code list identification code. Allowed code:"163" = Country sub-entity; state or province.


7/28/2019 Baplie30

36/88

SMDG


LOC (grp2) (Continued)

Remarks:1. If locodes other than UN-locodes are used the sender must verify with the recipient of the

message if other than UN-locodes are acceptable. Composites c519 and c553 are only relevantif no UN-locodes are used.

2. Minimum 2 ports to be given: loading port and discharging port.

3. Use of qualifiers, other than those for port of loading and port of discharge, must be agreedbetween partners.

Examples: Explanation:

#1:LOC+9+BEANR' loadport: Antwerp From Antwerp

LOC+11+IDJKT' disport: Jakarta to Jakarta,LOC+13+SGSIN' Transhipment port: Singapore via Singapore.

#2:LOC+9+BEANR' load port: Antwerp Same route: from AntwerpLOC+11+SGSIN' disport: Singapore to Singapore with on carriageLOC+83+IDJKT' Place of delivery: Jakarta to Jakarta.

#3:LOC+9+BEANR' load port: Antwerp Same route: From AntwerpLOC+11+IDJKT' disport: Jakarta to Jakarta,LOC+152+SGSIN' Next port of discharge: SIN via Singapore.

Note that examples #1, #2 and #3 look different, but contain identical route information, i.e. fromAntwerp to Jakarta with transhipment in Singapore.

Although in principle all three methods are allowed, SMDG recommends to use the method demonstratedin example # 1.


7/28/2019 Baplie30

37/88

SMDG



RFF (grp2)(M9)

+

c506.e1153(M an..3)

:

c506.e1154

'

REFERENCE (grp2)

Reference Code Qualifier: Allowed qualifiers:"BM" = B/L-number, as dummy, in case of ordinary cargo."ET" = Excess Transportation Number to be used for leading Stowage position, incase of Break bulk or odd-sized-cargo."ZZZ" = Mutually defined.

Reference identifier: For Qualifiers "BM" or "ZZZ": always "1".For Qualifier "ET": leading stowage location, containing relevant data for thisconsignment.

N.B. For break bulk and odd-sized-cargo see chapter 3: Special User Guidelines and examples.

Example: RFF+BM:1' or RFF+ET+0120106'

7/28/2019 Baplie30

38/88

SMDG


Group grp3

(C9) EQD - EQA NAD

EQD (grp3)

(M1)

+

e8053(M an..3)

+

c237.e8260

+

c224.e8155

++

EQUIPMENT DETAILS (grp3)

Equipment Type Code Qualifier: Allowed qualifiers:"CN" = Container"BB" = Break bulk"TE" = Trailer"ZZZ" = Ro/Ro or otherwise

Equipment Identifier:

1. The container number:Format: One continuous string with the identification, prefix and number. Examples:SCXU 2387653 must be transmitted as "SCXU2387653", EU 876 must betransmitted as "EU876". The number will be treated as a character string. E.g.alphanumeric check-digits can be transmitted here. If this segment is used the uniqueequipment identification number must always be transmitted, although this element isnot mandatory!

2. Break bulk: The break bulk reference number. The assigned break bulk referencenumbers must be agreed between partners.

3. Otherwise (Ro/Ro): The equipment identification number.

Equipment Size and Type Description Code ISO size-type code of4 digits (ISO 6346). Leave blank in case of break bulk.For unknown ISO size/type codes the following codes can be agreed between partners:"9999" = No information at all."4999" = Length = 40ft, rest unknown"2999" = Length = 20ft, rest unknown"4299" = 40ft 8'6", rest unknown"2299" = 20ft 8'6", rest unknown"4099" = 40ft 8'0", rest unknown

"2099" = 20ft 8'0", rest unknownOther codes to be agreed between partners.


7/28/2019 Baplie30

39/88

SMDG


EQD (grp3)

e8249(O an..3)

+

e8169(D an..3)

'

(Continued)

Equipment status code.1: Continental 11: Direct delivery2: Export 12: Bond transport

3: Import 13: Tranship to other vessel4: Remain on board 14: Tranship to other pier 5: Shifter 15: Rail road transport6: Transhipment 16: Road transport7: Hot delivery 17: Barge transport8: MLB 18: Temporary stowage9: MCB (Micro Land Bridge) 19: Urgent unpacking10: Canada Bound transport 20: Sea & Air

Full or Empty Indicator code. Allowed codes:"5" = Full

"4" = Empty.Leave blank in case of break bulk.

Remarks:1. This segment to be qualified with "BB" in case of a break bulk shipment, such as

EQD+BB+DEHAM00001'. The segment will be followed directly by NAD-segment. The NAD-segment which can be used to transmit the actual carrier of the break bulk.

2. Flats on which break bulk is stowed should be defined as 'empty'.

3. For a more detailed explanation of how to handle break bulk shipments please refer to chapter 3, firstparagraph "Break bulk cargo".


7/28/2019 Baplie30

40/88

SMDG


EQA (grp3)(C9)

+

e8053(M an..3)

+

c237.e8260(R an..17)

'

EQUIPMENT ATTACHED (grp3)

Equipment Type Code Qualifier: Allowed qualifiers:"RG" = Reefer Generator"CN" = Container"CH" = Chassis

Equipment Identifier: The unit number.

N.B. This segment may be used for transmission of attached equipment to container or for containersor other equipment stowed within one location with leading container in EQD (Platforms,Collapsible Flats, chassis, etc.).

Example of 5 (bundled or not) platforms stowed in one location:LOC+147+0120004::5'

MEA+WT++KGM:3250'LOC+9+GBFLS'LOC+11+JPYOK'RFF+BM:1'EQD+CN+ABCD 3223899+4361+++4' The first platform in the EQD-segmentEQA+CN+BCDE 4425399' The second in the first EQA...EQA+CN+CDEF 5534435' The third....EQA+CN+DEFG 6563535' The fourth...EQA+CN+EFGH 7663454' The fifth...

NAD+CF+ABC:172'

The first unit ABCD 3223899 identifies the whole set of 5 platforms and is stowed in the lowest position.

The others are stowed on top of the first unit (bundled or not). The sequence of the EQA-segments mayindicate the sequence of stowage, but this must be agreed between partners.Note that there is no separate indicator for bundles.


7/28/2019 Baplie30

41/88

SMDG


NAD (grp3)(C1)

+

e3035(M an..3)

+

c082.e3039

:

c082.e1131

(R an..17)

:

c082.e3055

'

NAME AND ADDRESS (grp3)

Party Function Code Qualifier: Allowed qualifier: "CA" (Carrier of the cargo).

Party Identifier: Name code of party responsible forthe carriage of the goods and/or equipment.

Code List Identification Code: Qualifier "172" (Carrier Code).

Code List Responsible Agency code. Allowed codes:20 = BIC (Bureau International des Containeurs)"166" = US National Motor Freight Classification Association (SCAC)"ZZZ" = Mutually agreed.

N.B. Name codes to be agreed with vessel operator, in case of Consortium.


7/28/2019 Baplie30

42/88

SMDG


Group grp4

(C999) DGS - FTX

DGS (grp4)(M1)

+

e8273(R an..3)

+

c205.e8351(M an..7)

:

c205.e8078(O an..7)

+

c234.e7124

+

c223.e7106

:

c223.e6411

+

DANGEROUS GOODS (grp4)

Dangerous Goods Regulations Code: Allowed Code "IMD" (IMO IMDG Code)

Hazard Identification Code: IMDG Code, e.g. "1.2" or "8".

Additional Hazard Classification Identifier: The IMDG code page number(English version).

United Nations Dangerous Goods (UNDG) Identifier: UN number of respectivedangerous cargo transported (4 digits).

Shipment Flashpoint Value: the actual flashpoint in degrees Celsius or Fahrenheit. Forinserting temperatures below zero or tenth degrees please refer to remarks under TMP-segment respectively to ISO 9735. If different dangerous goods with differentflashpoints within one load to be transported, only the lowest flashpoint should beinserted.

Measure Unit Code: Allowed codes:

"CEL" (degrees Celsius) = Preferred"FAH" (degrees Fahrenheit)


7/28/2019 Baplie30

43/88

SMDG


DGS (grp4)

e8339

(O an..3)

+

e8364(O an..6)

+

e8410(O an..4)

++

c235.e8158(O an..4)

:

c235.e8186(O an4)

+

c236.e8246

:

c236.e8246(O an..4)

:

(O an..4)

'

(Continued)

Packing danger level code: The packing group code of the hazardous

goods.

Emergency Procedure for Ships Identifier: Emergency schedule number.

Hazard Medical First Aid Guide Identifier. MFAG: Medical First Aid Guide number.

Orange Hazard Placard Upper Part Identifier.

Orange Hazard Placard Lower Part Identifier.

Dangerous Goods marking identifier (1).See below for possible use of this data element.

Dangerous Goods marking identifier (2).

Dangerous Goods marking identifier (3).


7/28/2019 Baplie30

44/88

SMDG


DGS (grp4) (Continued)

N.B. Use of this segment must be agreed between partners.

Possible use of data elements c.236.e8246 (1, 2 and 3):Code list of dangerous goods sub label:

Subsidiary riskExplosiveFlammable gas

Non-flammable compressed gasPoison gasFlammable liquidFlammable solid

Spontaneously combustibleDangerous when wetOxidizing agentToxicCorrosive

sub labelExplosiveFlammable gas

Non-flammable compressed gasPoison gasFlammable liquidFlammable solid

Spontaneously combustibleDangerous when wetOxidizing agentToxicCorrosive

code12.12.22.334.1

4.24.35.16.18


7/28/2019 Baplie30

45/88

SMDG


FTX (grp4)(C1)

+

e4451(M an..3)

+++

c108.e4440(1)

:

c108.e4440(2)

:

(O an..512)

'

FREE TEXT (grp4)

Text Subject Code Qualifier. Allowed qualifiers:"AAC" = Dangerous goods additional information"AAD" = Dangerous goods, technical name, proper shipping name.

Free text value: Description of hazard material in plain language.One element of maximum 70 characters to be given only for the description.

Transmit the text "NIL", if no description is available and one or both of thefollowing data elements must be transmitted.

Free text value: The net weight in kilos of the hazardous materialto be transmitted here.

Free text value: The DG-reference number as allocated by thecentral planner, if known.

N.B. Use of this segment must be agreed between partners.


7/28/2019 Baplie30

46/88

SMDG


UNT(M1)

+

e0074(M n..6)

+

e0062(M an..14)

'

MESSAGE TRAILER

Number of segments in the message, including UNH and UNTsegments, but excluding UNA, UNB and UNZ segments.

Message reference number: This reference must be identical tothe reference in the UNH-segment (e0062).


7/28/2019 Baplie30

47/88

SMDG


UNZ(M1)

+

e0036(M n..6)

+

e0020(M an..14)

'

INTERCHANGE TRAILER

Interchange Control Count: The number of messages in theinterchange.

Interchange Control Reference: This reference must beidentical to the reference in the UNB-segment (e0020).


7/28/2019 Baplie30

48/88

SMDG




7/28/2019 Baplie30

49/88

SMDG


5. SPECIAL USER GUIDELINES AND EXAMPLES

Breakbulk cargo (B/B)

Principle: For every piece of cargo in one stowage cell there has to be one grp2 occurrence.

A break bulk piece has to be described by one grp2 for every stowage cell which is used by this piece.The cargo is to be identified as B/B in segment FTX.All relevant information concerning the cargo has to be inserted under the "Leading Stowage Position"which is the first relevant stowage position mentioned within the sequence of a message irrespective of

possibly used equipment for this load. Segment RFF carries qualifier "ET" in e1153 and stowage positionin e1154 if more than one cell is occupied by this piece. Segment EQD carries qualifier "BB" in e8053and break bulk reference in e8260. The format of the break bulk reference is: "BB" concatenated withUN-Locode of POL concatenated with a five digit number, e.g. "BBDEHAM00001","BBNLRTM48901". This reference number is to be generated by the party which inserts the break bulk

piece into the message. The number must not be modified even if this piece is restowed.

The other used slots will just carry stowage position number and reference to "Leading Stowage Position"in segment RFF (same procedure as for odd-sized cargo: qualifier "ET" in e1153, stowage position ine1154) and break bulk reference as described above in segment EQD.

This is to be done for every single piece of break bulk.

Possibly used equipment (flatrack or platform) has to be described as any other container.Thus, in case of so-called "Sandwich-Stow" (Flat and Platform in one position) there have to be twooccurrences ofgrp2 for the used equipment (in addition of the grp2 which describes the break bulk).

See next pages for a detailed description of some examples.


7/28/2019 Baplie30

50/88

SMDG


Example # 1 a:

Breakbulk piece without any equipment.

1 piece of machinery 32500 kos, 890x250x320cm, from Hamburg to Singapore occupying bay 12 rows00,02,04 tier 06.

EDIFACT:

LOC+147+0120006::5'FTX+AAA+++1 PIECE MACHINERY'MEA+WT++KGM:32500'DIM+1+CMT:890:250:320'

LOC+9+DEHAM'LOC+11+SGSIN'RFF+ET:0120006'EQD+BB+DEHAM00001'

LOC+147+0120206::5'MEA+WT++KGM:0'RFF+ET:0120006'EQD+BB+DEHAM00001'

LOC+147+0120406::5'

MEA+WT++KGM:0'RFF+ET:0120006'EQD+BB+DEHAM00001'

Comment:

Leading cell positionIt is breakbulkWeight of the cargoMeasurements

Load portDischarge portReference to leading cell positionBreakBulk reference numberCarrier of the uncon piece

Next cell occupied by the pieceDummy segmentReference to leading cell positionBreakBulk reference number

Next cell occupied by the piece

Dummy segmentReference to leading cell positionBreakBulk reference number


7/28/2019 Baplie30

51/88

SMDG


Example # 1 b:

Two Breakbulk pieces without any equipment.Both of them sharing the same slots.

1 piece of machinery 32500 kos, 890x250x320cm, from Hamburgto Singapore occupying bay 12 rows 00,02,04 tier 06.

1 piece of machinery 25000 kos, 550x250x108, from Hamburgto Hongkong occupying bay 12 rows 00,02 tier 06.

EDIFACT:

FTX+AAA+++1 PIECE MACHINERY'MEA+WT++KGM:32500'DIM+1+CMT:890:250:320'LOC+9+DEHAM'LOC+11+SGSIN'RFF+ET:0120006'

NAD+CA+ABC:172:20'



MEA+WT++KGM:25000'DIM+1+CMT:550:250:108'LOC+9+DEHAM'LOC+11+HKHKG'RFF+ET:0120006'EQD+BB+DEHAM00003'

LOC+147+0120206::5'

RFF+ET:0120006'EQD+BB+DEHAM00003'

Comment:

Leading cell position of first breakbulk piece

It is breakbulkWeight of the cargoMeasurementsLoad portDischarge portReference to leading cell positionBreakBulk reference numberCarrier of the uncon piece



Leading cell position of second breakbulk pieceIt is breakbulkWeight of the cargoMeasurementsLoad portDischarge portReference to leading cell positionBreakBulk reference numberCarrier of the uncon piece



7/28/2019 Baplie30

52/88

SMDG


Example # 1 c:

One Breakbulk piece with equipment.

1 piece of machinery 32500 kos, 890x250x320cm, from Hamburg

to Singapore occupying bay 12 rows 00,02,04 tier 06.

Loaded on 3 flats number ECTU4235876 ECTU4246733 and ECTU4248891Tareweight of flats is 4250 kos each. The flats are loaded inHamburg. One flat will be discharged in Singapore. The other twoflats will be discharged in Tokyo.

EDIFACT:

LOC+147+0120006::5'FTX+AAA+++1 PIECE MACHINERY'

DIM+1+CMT:890:250:320'LOC+9+DEHAM'LOC+11+SGSIN'RFF+ET:0120006'

NAD+CA+ABC:172:20'


LOC+147+0120406::5'

RFF+ET:0120006'

LOC+147+0120006::5'MEA+WT++KGM:4250'LOC+9+DEHAM'LOC+11+SGSIN'RFF+BM:1'EQD+CN+ECTU 4235876+4361+++4'

NAD+CA+ABC:172:20'

Comment:

Leading cell positionIt is breakbulkWeight of the cargoMeasurementsLoad portDischarge portReference to leading cell positionBreakBulk reference numberCarrier of the uncon piece



Cell position of first flatWeight of the flatLoad portDischarge portDummy segmentFlat detailsCarrier of the flat


7/28/2019 Baplie30

53/88

SMDG


Example # 1 c: (continued)

LOC+147+0120206::5'

LOC+9+DEHAM'LOC+11+JPTYO'RFF+BM:1'EQD+CN+ECTU 4246733+4361+++4'

NAD+CA+XYZ:172:20'

LOC+147+0120406::5'MEA+WT++KGM:4250'

LOC+11+JPTYO'RFF+BM:1'

EQD+CN+ECTU 4248891+4361+++4'NAD+CA+PRQ:172:20'

Cell position of second flat

Weight of the flatLoad portDischarge portDummy segmentFlat detailsCarrier of the flat

Cell position of third flatWeight of the flatLoad portDischarge portDummy segment

Flat detailsCarrier of the flat


7/28/2019 Baplie30

54/88

SMDG


Example # 1 d:

One Breakbulk piece stowed on platforms and with upside down flatracks on top of it (sandwich stow).

One breakbulk piece of 105 tons from Hamburg to Singapore.Occupying bay 12 rows 00,02,04 tier 04. Loaded on 3 platforms and with 3 flatracks turned upside down ontop of it.

EDIFACT:

The breakbulk piece:

LOC+147+0120004::5'FTX+AAA+++1 PIECE MACHINERY'

MEA+WT++KGM:10500'DIM+1+CMT:890:440:290'LOC+9+DEHAM'LOC+11+SGSIN'RFF+ET:0120004'EQD+BB+DEHAM00005'

NAD+CA+ABC:172:20'

Additional slots occupied by the breakbulk piece:

LOC+147+0120204::5'MEA+WT++KGM:0'

RFF+ET:0120004'EQD+BB+DEHAM00005'


Supporting flatracks:

LOC+147+0120004::5'MEA+WT++KGM:3200'

LOC+9+DEHAM'LOC+11+SGSIN'RFF+BM:1'EQD+CN+HALO 4235876+4361+++4'

NAD+CA+ABC:172:20'

Comment:

Leading cell positionIt is breakbulk

Weight of the cargoMeasurementsLoad portDischarge portReference to leading cell positionBreakBulk reference numberCarrier of the uncon piece

Next cell occupied by the pieceDummy segment

Reference to leading cell positionBreakBulk reference number


Cell position of first flatrackWeight of the flatrack

Load portDischarge portDummy segmentFlatrack detailsCarrier of the flatrack


7/28/2019 Baplie30

55/88

SMDG


Example # 1 d: (continued)

LOC+147+0120204::5'

MEA+WT++KGM:3200'LOC+9+DEHAM'LOC+11+SGSIN'RFF+BM:1'EQD+CN+HALO 4246733+4361+++4'

NAD+CA+XYZ:172:20'

LOC+147+0120404::5'MEA+WT++KGM:3200'LOC+9+DEHAM'LOC+11+SGSIN'RFF+BM:1'

EQD+CN+HALO 4248891+4361+++4'NAD+CA+PRQ:172:20'

Supporting flatracks turned around:

LOC+147+0120006::5'FTX+SIN+++UPSIDE DOWN'MEA+WT++KGM:3250'LOC+9+DEHAM'LOC+11+SGSIN'RFF+BM:1'EQD+CN+ECTU 4235876+4361+++4'

NAD+CA+ABC:172:20'

LOC+147+0120206::5'FTX+SIN+++UPSIDE DOWN'MEA+WT++KGM:3250'LOC+9+DEHAM'LOC+11+SGSIN'RFF+BM:1'EQD+CN+ECTU 4246733+4361+++4'

NAD+CA+XYZ:172:20'

LOC+147+0120406::5'

FTX+SIN+++UPSIDE DOWN'MEA+WT++KGM:3250'LOC+9+DEHAM'LOC+11+SGSIN'RFF+BM:1'EQD+CN+ECTU 4248891+4361+++4'

NAD+CA+PRQ:172:20'

Cell position of second flatrack

Weight of the flatrackLoad portDischarge portDummy segmentFlatrack detailsCarrier of the flatrack

Cell position of third platformWeight of the flatrackLoad portDischarge portDummy segment

Flatrack detailsCarrier of the flatrack

Cell position of first flatrackOptional remarkWeight of the flatrackLoad portDischarge portDummy segmentFlatrack details

Carrier of the flatrack

Cell position of second flatrackOptional remarkWeight of the flatrackLoad portDischarge portDummy segmentFlatrack detailsCarrier of the flatrack

Cell position of third flat

Optional remarkWeight of the flatrackLoad portDischarge portDummy segmentFlatrack detailsCarrier of the flatrack


7/28/2019 Baplie30

56/88

SMDG


Example # 1 e:

One Breakbulk piece loaded on two platforms with wood in between (sandwich stow).

1 piece of machinery 32500 kgm, 890x250x220 cm, from Hamburg to Singapore occupying bay 12 row 00tier 06 loaded on two platforms number ECTU4246733 and ECTU4248891.Tareweight of the platforms is 4250 kgm each. The platforms have been loaded in Southampton and will bedischarged in Tokyo.

EDIFACT:

LOC+147+0120006::5'

FTX+AAA+++1 PIECE MACHINERY'MEA+WT++KGM:32500'DIM+1+CMT:890:250:220'LOC+9+DEHAM'LOC+11+SGSIN'RFF+ET:0120006'EQD+BB+DEHAM00004'

NAD+CA+ABC:172:20'

LOC+147+0120006::5'FTX+SIN+++SANDWICH STOW BOTTOM'MEA+WT++KGM:4250'LOC+9+GBSOU'LOC+11+JPTYO'RFF+BM:1'EQD+CN+ECTU 4246733+4960+++4'

NAD+CA+ABC:172:20'

LOC+147+0120006::5'FTX+SIN+++SANDWICH STOW TOP'MEA+WT++KGM:4250'LOC+9+GBSOU'LOC+11+JPTYO'RFF+BM:1'EQD+CN+ECTU 4248891+4960+++4'

NAD+CA+XYZ:172:20'

Comment:

Leading cell position

It is breakbulkWeight of the cargoMeasurementsLoad portDischarge portReference to leading cell positionBreakBulk reference numberCarrier of the uncon piece

Cell position of first platformOptional remarkWeight of the platformLoad portDischarge portDummy segmentPlatform detailsCarrier of the platform

Cell position of second platformOptional remarkWeight of the platformLoad portDischarge portDummy segmentPlatform detailsCarrier of the platform


7/28/2019 Baplie30

57/88

SMDG




7/28/2019 Baplie30

58/88

SMDG


6. MESSAGE STRUCTURE DIAGRAM


7/28/2019 Baplie30

59/88

SMDG




7/28/2019 Baplie30

60/88

SMDG


7. SEGMENT DIRECTORY (D.00B)

BGM BEGINNING OF MESSAGE

Function: To indicate the type and function of a messageand to transmit the identifying number.

010 C002 DOCUMENT/MESSAGE NAME C 11001 Document name code C an..31131 Code list identification code C an..173055 Code list responsible agency code C an..31000 Document name C an..35

020 C106 DOCUMENT/MESSAGE IDENTIFICATION C 11004 Document identifier C an..351056 Version identifier C an..91060 Revision identifier C an..6

030 1225 MESSAGE FUNCTION CODE C 1 an..3

040 4343 RESPONSE TYPE CODE C 1 an..3


7/28/2019 Baplie30

61/88

SMDG


DGS DANGEROUS GOODS

Function: To identify dangerous goods.

010 8273 DANGEROUS GOODS REGULATIONS CODE C 1 an..3

020 C205 HAZARD CODE C 18351 Hazard identification code M an..78078 Additional hazard classification

identifier C an..78092 Hazard code version identifier C an..10

030 C234 UNDG INFORMATION C 17124 United Nations Dangerous Goods (UNDG)

identifier C n47088 Dangerous goods flashpoint value C an..8

040 C223 DANGEROUS GOODS SHIPMENT FLASHPOINT C 17106 Shipment flashpoint value C n36411 Measurement unit code C an..3

050 8339 PACKAGING DANGER LEVEL CODE C 1 an..3

060 8364 EMERGENCY PROCEDURE FOR SHIPS IDENTIFIER C 1 an..6

070 8410 HAZARD MEDICAL FIRST AID GUIDE IDENTIFIER C 1 an..4

080 8126 TRANSPORT EMERGENCY CARD IDENTIFIER C 1 an..10

090 C235 HAZARD IDENTIFICATION PLACARD DETAILS C 18158 Orange hazard placard upper part

identifier C an..48186 Orange hazard placard lower part

identifier C an4

100 C236 DANGEROUS GOODS LABEL C 18246 Dangerous goods marking identifier C an..48246 Dangerous goods marking identifier C an..48246 Dangerous goods marking identifier C an..4

110 8255 PACKING INSTRUCTION TYPE CODE C 1 an..3

120 8325 HAZARDOUS MEANS OF TRANSPORT CATEGORY CODE C 1 an..3

130 8211 HAZARDOUS CARGO TRANSPORT AUTHORISATIONCODE C 1 an..3


7/28/2019 Baplie30

62/88

SMDG


DIM DIMENSIONS

Function: To specify dimensions.

010 6145 DIMENSION TYPE CODE QUALIFIER M 1 an..3

020 C211 DIMENSIONS M 16411 Measurement unit code M an..36168 Length dimension value C n..156140 Width dimension value C n..156008 Height dimension value C n..15

DTM DATE/TIME/PERIOD

Function: To specify date, and/or time, or period.

010 C507 DATE/TIME/PERIOD M 1

2005 Date or time or period function codequalifier M an..3

2380 Date or time or period value C an..352379 Date or time or period format code C an..3

EQA ATTACHED EQUIPMENT

Function: To specify attached or related equipment.

010 8053 EQUIPMENT TYPE CODE QUALIFIER M 1 an..3

020 C237 EQUIPMENT IDENTIFICATION C 18260 Equipment identifier C an..171131 Code list identification code C an..173055 Code list responsible agency code C an..33207 Country name code C an..3


7/28/2019 Baplie30

63/88

SMDG


EQD EQUIPMENT DETAILS

Function: To identify a unit of equipment.

010 8053 EQUIPMENT TYPE CODE QUALIFIER M 1 an..3

020 C237 EQUIPMENT IDENTIFICATION C 18260 Equipment identifier C an..171131 Code list identification code C an..173055 Code list responsible agency code C an..33207 Country name code C an..3

030 C224 EQUIPMENT SIZE AND TYPE C 18155 Equipment size and type description code C an..101131 Code list identification code C an..173055 Code list responsible agency code C an..38154 Equipment size and type description C an..35

040 8077 EQUIPMENT SUPPLIER CODE C 1 an..3

050 8249 EQUIPMENT STATUS CODE C 1 an..3

060 8169 FULL OR EMPTY INDICATOR CODE C 1 an..3

FTX FREE TEXT

Function: To provide free form or coded text information.

010 4451 TEXT SUBJECT CODE QUALIFIER M 1 an..3

020 4453 FREE TEXT FUNCTION CODE C 1 an..3

030 C107 TEXT REFERENCE C 14441 Free text value code M an..171131 Code list identification code C an..173055 Code list responsible agency code C an..3

040 C108 TEXT LITERAL C 14440 Free text value M an..5124440 Free text value C an..5124440 Free text value C an..5124440 Free text value C an..5124440 Free text value C an..512

050 3453 LANGUAGE NAME CODE C 1 an..3

060 4447 FREE TEXT FORMAT CODE C 1 an..3

GDS NATURE OF CARGO

Function: To indicate the type of cargo as a generalclassification.

010 C703 NATURE OF CARGO C 1


7/28/2019 Baplie30

64/88

SMDG


7085 Cargo type classification code M an..31131 Code list identification code C an..173055 Code list responsible agency code C an..3


7/28/2019 Baplie30

65/88

SMDG


GID GOODS ITEM DETAILS

Function: To indicate totals of a goods item.

010 1496 GOODS ITEM NUMBER C 1 n..5

020 C213 NUMBER AND TYPE OF PACKAGES C 17224 Package quantity C n..87065 Package type description code C an..171131 Code list identification code C an..173055 Code list responsible agency code C an..37064 Type of packages C an..357233 Packaging related description code C an..3

030 C213 NUMBER AND TYPE OF PACKAGES C 17224 Package quantity C n..87065 Package type description code C an..171131 Code list identification code C an..17

3055 Code list responsible agency code C an..37064 Type of packages C an..357233 Packaging related description code C an..3

040 C213 NUMBER AND TYPE OF PACKAGES C 17224 Package quantity C n..87065 Package type description code C an..171131 Code list identification code C an..173055 Code list responsible agency code C an..37064 Type of packages C an..357233 Packaging related description code C an..3

050 C213 NUMBER AND TYPE OF PACKAGES C 1

7224 Package quantity C n..87065 Package type description code C an..171131 Code list identification code C an..173055 Code list responsible agency code C an..37064 Type of packages C an..357233 Packaging related description code C an..3

060 C213 NUMBER AND TYPE OF PACKAGES C 17224 Package quantity C n..87065 Package type description code C an..171131 Code list identification code C an..173055 Code list responsible agency code C an..37064 Type of packages C an..35

7233 Packaging related description code C an..3


7/28/2019 Baplie30

66/88

SMDG


LOC PLACE/LOCATION IDENTIFICATION

Function: To identify a place or a location and/or relatedlocations.

010 3227 LOCATION FUNCTION CODE QUALIFIER M 1 an..3

020 C517 LOCATION IDENTIFICATION C 13225 Location name code C an..251131 Code list identification code C an..173055 Code list responsible agency code C an..33224 Location name C an..256

030 C519 RELATED LOCATION ONE IDENTIFICATION C 13223 First related location name code C an..251131 Code list identification code C an..173055 Code list responsible agency code C an..33222 First related location name C an..70

040 C553 RELATED LOCATION TWO IDENTIFICATION C 13233 Second related location name code C an..251131 Code list identification code C an..173055 Code list responsible agency code C an..33232 Second related location name C an..70

050 5479 RELATION CODE C 1 an..3

MEA MEASUREMENTS

Function: To specify physical measurements, includingdimension tolerances, weights and counts.

010 6311 MEASUREMENT PURPOSE CODE QUALIFIER M 1 an..3

020 C502 MEASUREMENT DETAILS C 16313 Measured attribute code C an..36321 Measurement significance code C an..36155 Non-discrete measurement name code C an..176154 Non-discrete measurement name C an..70

030 C174 VALUE/RANGE C 16411 Measurement unit code M an..3

6314 Measurement value C an..186162 Range minimum value C n..186152 Range maximum value C n..186432 Significant digits quantity C n..2

040 7383 SURFACE OR LAYER CODE C 1 an..3


7/28/2019 Baplie30

67/88

SMDG


NAD NAME AND ADDRESS

Function: To specify the name/address and their relatedfunction, either by C082 only and/orunstructured by C058 or structured by C080 thru

3207.

010 3035 PARTY FUNCTION CODE QUALIFIER M 1 an..3

020 C082 PARTY IDENTIFICATION DETAILS C 13039 Party identifier M an..351131 Code list identification code C an..173055 Code list responsible agency code C an..3

030 C058 NAME AND ADDRESS C 13124 Name and address description M an..353124 Name and address description C an..353124 Name and address description C an..35

3124 Name and address description C an..353124 Name and address description C an..35

040 C080 PARTY NAME C 13036 Party name M an..353036 Party name C an..353036 Party name C an..353036 Party name C an..353036 Party name C an..353045 Party name format code C an..3

050 C059 STREET C 13042 Street and number or post office box

identifier M an..353042 Street and number or post office boxidentifier C an..35

3042 Street and number or post office boxidentifier C an..35

3042 Street and number or post office boxidentifier C an..35

060 3164 CITY NAME C 1 an..35

070 C819 COUNTRY SUB-ENTITY DETAILS C 13229 Country sub-entity name code C an..91131 Code list identification code C an..17

3055 Code list responsible agency code C an..33228 Country sub-entity name C an..35

080 3251 POSTAL IDENTIFICATION CODE C 1 an..17

090 3207 COUNTRY NAME CODE C 1 an..3

RFF REFERENCE

Function: To specify a reference.

010 C506 REFERENCE M 1

1153 Reference code qualifier M an..3


7/28/2019 Baplie30

68/88

SMDG


1154 Reference identifier C an..701156 Document line identifier C an..64000 Reference version identifier C an..351060 Revision identifier C an..6

RNG RANGE DETAILS

Function: To identify a range.

010 6167 RANGE TYPE CODE QUALIFIER M 1 an..3

020 C280 RANGE C 16411 Measurement unit code M an..36162 Range minimum value C n..186152 Range maximum value C n..18

TDT DETAILS OF TRANSPORT

Function: To specify the transport details such as mode oftransport, means of transport, its conveyancereference number and the identification of themeans of transport.The segment may be pointed to by the TPLsegment.

010 8051 TRANSPORT STAGE CODE QUALIFIER M 1 an..3

020 8028 MEANS OF TRANSPORT JOURNEY IDENTIFIER C 1 an..17

030 C220 MODE OF TRANSPORT C 18067 Transport mode name code C an..38066 Transport mode name C an..17

040 C228 TRANSPORT MEANS C 18179 Transport means description code C an..88178 Transport means description C an..17

050 C040 CARRIER C 1

3127 Carrier identifier C an..171131 Code list identification code C an..173055 Code list responsible agency code C an..33128 Carrier name C an..35

060 8101 TRANSIT DIRECTION INDICATOR CODE C 1 an..3

070 C401 EXCESS TRANSPORTATION INFORMATION C 18457 Excess transportation reason code M an..38459 Excess transportation responsibility code M an..37130 Customer shipment authorisation

identifier C an..17

080 C222 TRANSPORT IDENTIFICATION C 1


7/28/2019 Baplie30

69/88

SMDG


8213 Transport means identification nameidentifier C an..9

1131 Code list identification code C an..173055 Code list responsible agency code C an..38212 Transport means identification name C an..35

8453 Transport means nationality code C an..3

090 8281 TRANSPORT MEANS OWNERSHIP INDICATOR CODE C 1 an..3


7/28/2019 Baplie30

70/88

SMDG


TMP TEMPERATURE

Function: To specify the temperature setting.

010 6245 TEMPERATURE TYPE CODE QUALIFIER M 1 an..3

020 C239 TEMPERATURE SETTING C 16246 Temperature value C n..156411 Measurement unit code C an..3


7/28/2019 Baplie30

71/88

SMDG


Service segments ISO 9735:

Segment: UNB, Interchange Header

Function: To start, identify and specify an interchange

Ref. Repr. Name Remarks

S001 M SYNTAX IDENTIFIER0001 a4 M Syntax identifier a3, upper case

Controlling Agency (e.g.UNO=UN/ECE) and a1 statinglevel (e.g. A) (whichtogether give UNOA)

0002 n1 M Syntax version number Increments 1 for each newversion. Shall be 2 toindicate this version

___________________________________________________________________

S002 M INTERCHANGE SENDER0004 an..35 M Sender identification Code or name as specified

in IA0007 an..4 C Partner identification Used with sender

code qualifier identification code0008 an..14 C Address for reverse

routing___________________________________________________________________

S003 M INTERCHANGE RECIPIENT0010 an..35 M Recipient Identification Code or name as

specified in IA0007 an..4 C Partner identification Used with recipient

code qualifier identification code0014 an..14 C Routing address If used, normally coded

sub-address for onwardrouting

___________________________________________________________________

S004 M DATE/TIME OF PREPARATION0017 n6 M Date YYMMDD0019 n4 M Time HHMM___________________________________________________________________

0020 an..14 M INTERCHANGE CONTROL Unique referenceREFERENCE assigned by sender___________________________________________________________________

S005 C RECIPIENTS REFERENCE,PASSWORD

0022 an..14 M Recipient's reference/ As specified in IA. Maypassword be password to

recipient's system or tothird party network

0025 an2 C Recipient's reference/ If specified in IApassword qualifier

___________________________________________________________________


7/28/2019 Baplie30

72/88

SMDG


0026 an..14 C APPLICATION REFERENCE Optionally messageidentification if theinterchange containsonly one type ofmessage

___________________________________________________________________

0029 a1 C PROCESSING PRIORITY CODE Used if specified in IA___________________________________________________________________

0031 n1 C ACKNOWLEDGEMENT REQUEST Set = 1 if senderrequestsacknowledgement, i.e.UNB and UNZsegments receivedand identified

___________________________________________________________________

0032 an..35 C COMMUNICATIONS AGREEMENT If used, to identifyID type of communicationagreement controllingthe interchange,e.g. Customs or ECEagreement. Code orname as specified in IA

___________________________________________________________________

0035 n1 C TEST INDICATOR Set = 1 if theinterchange is a test.Otherwise not usedused


7/28/2019 Baplie30

73/88

SMDG


Segment: UNH, Message Header

Function: To head, identify and specify a Message


0062 an..14 M MESSAGE REFERENCE NUMBER A sender's uniquemessage reference

___________________________________________________________________

S009 M MESSAGE IDENTIFIER0065 an..6 M Message type Type of message being

transmitted0052 an..3 M Message version number Version number of the

message type. If UNG isused, 0052 shall beidentical

0054 an..3 M Message release number Release number withincurrent version number0051 an..2 M Controlling agency Code to identify the

agency controlling thespecification,maintenance andpublication of themessage type

0057 an..6 C Association assigned A code assignedcode by the association

responsible for thedesign and maintenanceof the message type

___________________________________________________________________

0068 an..35 C COMMON ACCESS REFERENCE Key to relate allsubsequent transfers ofdata to the samebusiness case offile. Within the35 characters theIA may specifycomponent elements

___________________________________________________________________

S010 C STATUS OF THE TRANSFER

0070 n..2 M Sequence of transfers Starts at 1 and isincremented by 1 foreach transfer

0073 a1 C First and last transfer C = Creation, must bepresent for firsttransfer if more thanone foreseenF = Final, must bepresent for lasttransfer

*) Not required if provided in UNG


7/28/2019 Baplie30

74/88

SMDG


Segment: UNT, Message Trailer

Function: To end and check the completeness of a Message


0074 n..6 M NUMBER OF SEGMENTS IN THE Control countMESSAGE including UNH and UNT

___________________________________________________________________

0062 an..14 M MESSAGE REFERENCE NUMBER Shall be identical to0062 in UNH

Segment: UNZ, Interchange Trailer

Function: To end and check the completeness of an interchange


0036 n..6 M INTERCHANGE CONTROL COUNT The count of the numberof messages or, ifused, the number offunctional groups inthe interchange.One of these countsshall appear.

___________________________________________________________________

0020 an..14 M INTERCHANGE CONTROL Shall be identical to

REFERENCE 0020 in UNB


7/28/2019 Baplie30

75/88

SMDG


8. SMDG EDI-ELECTRONIC DATA INTERCHANGE UNDERSTANDING

This draft is the result of work carried out by a SMDG-Subgroup. It was set up mainly onTEDIS drafts (May 1991/January 1994) but ideas and comments of EDI Council of Canada,

American Bar Association, UN/ECE Recommendations and German DIN also were taken intoaccount. So - in general - this draft can be seen as a globally oriented Understanding.

Version 1

September 1994


7/28/2019 Baplie30

76/88

SMDG


SMDG EDI-ELECTRONIC DATA INTERCHANGE UNDERSTANDING

0. Introduction

The terms and conditions of this Understanding which can be used in bilateral or multilateral EDIrelationships shall govern the conduct and methods of operation between the Parties in relation to theinterchange of data by tele-transmission for the purpose of or associated with the supply of vessel, inlandcarriers and container related data. They take account of the Uniform Rules of Conduct for Interchange ofTrade Data by Tele-transmission as adopted by the International Chamber of Commerce and inconjunction with the TEDIS Program European Model EDI Agreement. The Understanding is consideredto be a contractual framework setting out intentions and clarifying rights and obligations. If necessaryadditional rules might be agreed between Parties, these rules are specific/bilateral and can be worked outin an appendix. Parties in this Understanding are:

Shipping Lines; Agents; Container Terminals; Stevedores, Inland Carriers, etc.(Detail of the parties: see enclosure A)


7/28/2019 Baplie30

77/88

SMDG


SMDG EDI-ELECTRONIC DATA INTERCHANGE UNDERSTANDING

1. Definitions

For the purposes of the EDI Understanding the following definitions shall apply:

Acknowledgment of Receipt:A message acknowledging or rejecting, with error indication, a received interchange, a functional group ora message.

Message verificationMessage verification includes the identification, authentication and verification of the integrity and originof a message by use of an authentication mechanism such as a digital signature and/or any alternativesecurity means or procedures to establish that a message is genuine.

Adopted protocolAn accepted method for the interchange of messages based on the UN/EDIFACT standard (agreedversion) for the presentation and structuring of the transmission of messages, or such other protocol asmay be agreed in writing by the Parties.

Data TransferOne more EDI-messages sent together as one unit of transmission, which includes the heading andtermination data in accordance with UN/EDIFACT.

DaysAny day.

Data LogThe complete historical and chronological record of interchanged data representing the messagesinterchanged between the Parties.

EDIElectronic Data Interchange is the transmission of data structured according to agreed message standards,

between information systems, by electronic means.

EDI messageA coherent set of data, structured according to agreed message standards, for transmission by electronicmeans, prepared in a computer readable format and capable of being automatically and unambiguously

processed.

Technical Annex (see enclosure B)The Technical Annex consists of:

User manual (for example for BAPLIE, MOVINS, TANSTA), a handbook with message specificationsas descriptions of data elements, segments, and data structures.

Technical specifications as systems operation, methods of transmission, third Party providers.

Procedural/organizational rules: E.g. the communication pattern between a stowage center and a memberof related container terminals; acknowledgement of receipt, message verification.

UN/EDIFACTThe United Nations rules for Electronic Data Interchange for Administration, Commerce and Transport,


7/28/2019 Baplie30

78/88

SMDG


comprising a set of internationally agreed standards, directories and guidelines for the electronicinterchange of structured data, and in particular, interchange related to trade and goods and services,

between independent and computerized information systems.

2. Object and Scope

The provisions contained in this EDI Understanding shall govern the exchange of EDI messages betweennamed Parties.

The provision of the Technical Annex form an integral part of the EDI Understanding. Accordingly, thebreach of any of the provisions contained within the Technical Annex shall be a breach of the EDIUnderstanding itself.

When Parties mutually agree in writing upon additional provisions to this Understanding, such provisionsshall form an integral part of this Understanding.

Parties agree that all EDI Messages shall be transmitted in accordance with the provisions of the adoptedprotocol for Data Interchange, as specified in the Technical Annex.

3. Applicability

The Container Handling Agreement covers all contingencies not covered and/or addressed in this EDIUnderstanding. In case of non conformity of this EDI Understanding and the Container HandlingAgreement, this EDI Understanding shall prevail in respect of data interchange only.

4. Operational Requirements for EDI

4.1 Message Standards

All EDI messages shall be transmitted in accordance with the UN/EDIFACT standards (EDIFACTsyntax rules ISO 9735, latest version) and recommendations and their updated versions, as approved and

published by the United Nations Economic Commission for Europe (UN/ECE) in the United NationsTrade Data Interchange Directory (UNTDID), details of which are set out in the technical annex - partUSER MANUAL.

4.2 Systems Operation

The Parties shall provide and maintain, to the level specified in the Technical Annex, the equipment(hardware), software and services necessary to effectively transmit, receive, log and store EDI messages.

4.3 Method of Transmission

The Parties shall agree between themselves a method of transmission and, if required, use the services ofThird Party Network Providers.

4.4 Specifications

All specifications and details regarding 4.1., 4.2., and 4.3., shall be as set out in the Technical Annex.The Parties shall conduct such tests as may be mutually defined from time to time to establish and


7/28/2019 Baplie30

79/88

SMDG


monitor the adequacy of the standards, hardware, software, protocols, services or any of the relevantspecifications for the purpose of this Understanding.

5. Acknowledgement of Receipt of EDI Messages

5.1 In addition to the acknowledgements included in the telecommunication protocols, the Partiesmay agree that the receiver of an EDI Message sends an acknowledgement of receipt of the message.Alternatively the Parties may define in the Technical Annex, the extent to which any messages sent andreceived will be subject to an acknowledgement of receipt. A message to be acknowledged must not beacted upon before complying with the request for an acknowledgement.

5.2 If Parties mutually agree upon an acknowledgement of receipt this acknowledgement of receiptof an EDI message shall be send in such time as is defined in the Technical Annex. In the event that nospecific time limits have been agreed or stated in the Technical Annex, the acknowledgement shall be sendwithin one working day following the day of receipt of the EDI message to be acknowledged.

5.3 If the sender does not receive the acknowledgement of receipt within the time limit, he may,upon giving notification to the receiver to that effect, treat the Message as null and void as from theexpiration of that time limit or initiative an alternative recovery procedure as specified in the TechnicalAnnex, to ensure effective receipt of the acknowledgement.

In case of failure of recovery procedure, within the time limit, the Message will definitely be treated asnull and void, as from the expiration ot that time limit, upon notification to the receiver.

6. Processing of EDI Messages

The Parties undertake to process or ensure their system processes the EDI messages within any timelimits specified in the Technical Annex, or as agreed between the Parties, or in the absence of such, assoon as possible.

7. Security of EDI Messages

The Parties will only be responsible and liable for breaking the rules of verification, identification andauthentication in case of gross negligence or willful misconduct.

7.1 The Parties undertake to implement and maintain control and security procedures and measuresnecessary to ensure the protection of messages against the risk of unauthorized access, loss or destruction.

7.2 In addition to the elements of control relevant for EDI messages provided by the UN/EDIFACTrules, the Parties shall agree on procedures or methods to ensure message verification. The specificationsrelating to the message verification should be set out in the Technical Annex.

When message verification results in the rejection of, or the detection of an error in an EDI message, thereceiver will inform the sender thereof within the time limits specified in the Technical Annex or agreed

between the Parties, provided the sender is identified, and will not act upon the message before receivinginstructions to do so, from the sender.

If a sender of an EDI Message includes non modified data from a previous EDI Message into a new EDIMessage, the sender is not liable for the completeness and accuracy of this non-modified data.


7/28/2019 Baplie30

80/88

SMDG


7.3 For security purposes, the Parties may agree to use a specific form of protection for certainmessages such as a method of encryption or any other method agreed between the Parties, as long as it is

permitted by law. The s

Date post:	03-Apr-2018
Category:	Documents
Upload:	ksenthil77
View:	217 times
Download:	0 times

Baplie30

Documents