140v10

7/28/2019 140v10

1/59

PRINCIPLES AND RULES

FOR THE

IMPLEMENTATION OFTRANSPORT EDI MESSAGES

BERTH

MANAGEMENT(BERMAN MESSAGE)

BASED ON THE UN/EDIFACT -D98B

BERMAN MESSAGE

DOCUMENT REFERENCE : D4/ITIGG/140/v.1.0

Authorised and Issued by the UN/EDIFACT JRT Message Development Group 4

(Transport), through its ITIGG sub-group (the International TransportImplementation Guidelines Group)

VERSION 1.0 May 11th 1999

7/28/2019 140v10

2/59

INTERNATIONAL TRANSPORT IMPLEMENTATION GUIDELINES GROUP 18

PRINCIPLES AND RULES FOR MARITIME IMPLEMENTATION OF

TRANSPORT EDI MESSAGES

BERTH MANAGEMENT

(BERMAN MESSAGE)

INTRODUCTION

SCOPE OF THIS DOCUMENT

This document has been developed by the International Transport Implementation Guidelines Group (ITIGG)

and covers maritime-related electronic data interchange (EDI). Specifically it provides guidance as to therecommended usage within the UN/EDIFACT BERMAN message of codes, qualifiers, data elements,

composites, segments and groups of segments for international trade purposes.

The intention is to provide principles and rules to ensure consistent use throughout the worldwide trade andtransport community of such trade data.

By establishing this consistency, trade and transport organisations and their supporting software developersand value-added network suppliers can develop products and services incorporating EDI messages which will

be interchangeable and readable by other like services throughout the world.

DOCUMENT REFERENCE

The number of this document is D4/ITIGG/140 which refers to document number 140 prepared by the

UN/EDIFACT Development Group 4 (D4) (Joint Message Development Group 4 (Transport)), through itsInternational Transport Implementation Guidelines Sub-Group.

UN/EDIFACT DIRECTORY REFERENCE

This document is based on the UN/EDIFACT D98B directory. This directory has been designated by D4

(Transport) as the basis for all global implementations and associated guidelines for this message.

PRINCIPLES & RULES FOR IMPLEMENTATION BERTH MANAGEMENT Version 0.0 September 1998

7/28/2019 140v10

3/59


COMPLIANCE WITH ITIGG PRINCIPLES AND RULES

At its Helsinki meeting in September 1996, D4/ITIGG agreed on specific conditions for compliance with the

Principles and Rules laid out in this document. These conditions take the form of Recommendation D4/50,

which reads as follows:

D4 recommends that user groups use the documents issued by ITIGG for Principles and Rules (P&R)for specific sets of messages to the fullest extent possible.

1.0 D4 allows user groups to describe their specific Message Implementation Guidelines (MIGs)

as compliant with the ITIGG Principles and Rules document Version *.*provided that:

1.1 The usage indicators in the user group MIG are derived from the relevant Principles and

Rules document according to the following rule:

Usage Indicator Usage Indicator Usage Indicator

in UNSM in P&R document in specific MIG

Mandatory (M) Mandatory (M) always Mandatory (M)Conditional (C) Required (R) always Required (R)

Conditional (C) Advised (A) may be Dependent, Required or,

Optional (D,R,O)

Conditional (C) Dependent (D) may be Dependent, Required,Optional or Not Used (D,R,O,X)

Conditional (C) Optional(O) may be Optional, Dependent,

Required or Not Used (O,D,R,X)Conditional (C) Not Used (X) always Not Used (X)

1.2 The General Recommendations approved by D4 and issued through ITIGG are followed.

1.3 The code values and qualifier values in the specific MIG should be chosen from those

recommended by ITIGG in the relevant P&R Document.

1.4 Where these conditions are followed, the Guideline may be identified with the appropriate

ITIGG version code (ITG**) in date element 0057 of the UNH.

2.0 In case user groups feel the need to deviate from the above compliance conditions anImplementation Change Request (ICR) is to be put forward to the regional UN/EDIFACT

Transport Group. Where a guideline is published which does not comply with these

conditions data element 0057 should not contain the ITIGG code.

3.0 When agreed in ITIGG the ICR will be incorporated in the next release of the relevant P&R

document.

The specific MIG is to be identified in DE 0057 in accordance with the rules set out in General

Recommendation D4/5.


7/28/2019 140v10

4/59


BACKGROUND

It was the development of UN/EDIFACT messages in the Transport sector which initiated the formation of a

global UN EDI standards organisation and this development has continued to progress from the inception of

the UN/EDIFACT standard to the present time.

Message structures essential to the use of electronic commerce in the Transport sector have been agreed andapproved by the relevant authorities up to and including Working Party 4 (Trade Facilitation) of UN/ECE.Over the past five years these messages have been implemented by various communities in the six

UN/EDIFACT regions.

These existing implementations have, in most cases, developed in isolation and this has resulted in differinginterpretations of the standard messages. In turn this has resulted in a lack of international synergy with

regards to the use of codes, qualifiers, data elements, composites, segments, groups of segments and even the

messages themselves.

The UN/EDIFACT Joint Message Development Group for Transport (D4) has recognised that this lack of

synergy represents a serious inhibitor to the growth of global electronic commerce.

As the harmonisation of implementation guidelines of UN/EDIFACT messages was not a formal work task of

the Joint Rapporteurs Team (JRT) meeting - its purpose was to establish and maintain message structures and

data directories - the interested members of D4 (Transport) formed an informal group to attempt to harmoniseknown message implementation guides and user manuals and to provide a basis for intending implementers to

proceed with confidence.

In late 1994 and early 1995 the group met informally to make recommendations on how codes, qualifiers,elements, segments and messages should be used. The progress made by this relatively small group of experts

(less than 20) encouraged the group to formally establish itself as the International Transport Implementation

Guidelines Group (ITIGG).

The aims and existence of ITIGG were announced after a meeting in Oakland, CA in July 1995. It was agreed

that ITIGG would set itself the major objective of compiling and issuing a document in the first quarter of1996 which would provide the principles and rules for the international implementation of electronic messagesin the transport industry. This document which deals primarily with the maritime sector, represents the

achievement of that objective. The future objectives of ITIGG are to incorporate the work of harmonising

guidelines from other modes of transport covering air, road, rail and other means of inland transport.

At the UN/EDIFACT Joint Rapporteurs Team meeting in Oxford UK in September 1995, the D4 (Transport)

work group decided to recognise ITIGG as the source of guideline harmonisation information and leadership.

D4 also took a decision to officially accept ITIGG as a sub-group of D4 (Transport).

Furthermore the D4 (Transport) Group at the Oxford JRT meeting has requested the Rapporteurs - through

their Co-Chairman - to formally include the work of harmonising implementation guidelines in the scope of

the re-engineered UN/EDIFACT process.

At the Helsinki JRT meeting in September 1996 it was agreed that a formal working group should be

established within the JRT process to commence the work of comparing and harmonising segment usagebetween different industry sectors. This has received the endorsement of other key working groups within

UN/EDIFACT.


7/28/2019 140v10

5/59


STATUS INDICATORS AND USAGE INDICATORS

Status Indicators

Status Indicators (M and C) form part of the UN/EDIFACT standard and indicate a minimum requirement tofulfil the needs of the message structure.

The Status Indicators are:-

Value Description

M Mandatory

This entity must appear in all messages. Shown as Usage Indicator "M" in

Implementation Guidelines.

C Conditional

This entity is used by agreement between the parties to the transaction.

A 'Conditional' Status Indicator may be represented by a supporting Usage Indicator which is either R, A, D, O

or X (see below)

Usage Indicators

Throughout this document reference is made to indicators (R, A, D, O and X) which are shown adjacent todata items and which dictate for the particular message or set thereof the agreed usage of the data items or

entities.

Set out below are the indicators and their respective uses:-

Value Description

M Mandatory

Indicates that this item is mandatory in the message.

R Required

Indicates that this entity must be sent in this implementation.

A Advised

Indicates that a globally recognised codeset i.e. UN or ISO code set etc. is highlyrecommended for use in this implementation over any local codes which can usuallybe advised in a different data element for addititional identification if required.

D Dependent

Indicates that the use of the entity depends upon a well-defined condition or set of

conditions. These conditions must be clearly specified in the relevant

implementation guideline.

O Optional

Indicates that this entity is at the need or discretion of the sender of the message.


7/28/2019 140v10

6/59


X Not Used

Indicates that the entity is not to be used is this message implementation.

Where an element within a composite is marked M or R, but the composite has been marked O or D, this

indicates that the element must always be transmitted only if the composite is used.

Implementers are advised to include the above information on Usage and Status Indicators in their

Implementation Guidelines.

DOCUMENT MAINTENANCE

The data content of this document has been prepared and approved by UN/EDIFACT D4/ITIGG and no

alteration may be made to the content of this document without reference to and approval of D4/ITIGG.

Any remarks, questions, amendments or requested alterations to this document are to be addressed to:-

ITIGG Secretariat

Internet: [email protected]

WWW: www.tradegate.org.au/newitigg/newitigg-main.htm

preferably via the UN/EDIFACT Transport Work Group / Message Design Group in the requestor's region.


7/28/2019 140v10

7/59


THE BERMAN MESSAGE

The official UN/EDIFACT documentation for the D98B version of the BERMAN message describes the

message as follows:

1.1 Functional Definition

The berth management message is a message from a shipping agent or liner agent to the Authority responsiblefor berthing allowances, normally Port Authority, requesting a berth, giving details of the call, vessel, berth

requirements and expected operations.

SHIP AGENT PORT AUTHORITYBERTH REQUEST >

< ACKNOWLEDGMENT

1.2 Field of Application

The Berth Management message may be used for both national and international trade. It is based on universalcommercial practice and is not dependent on the type of business or industry.

1.3 Principles

This message is meant to comply with requirements of authorities concerning the request for berthing

services. The following guidelines, rules and functionality apply to this Berth management message:

1- A message will contain information on only one means of transport/conveyance.

2- A ship call may requires several berths

3- One berth may be the scenario of several operations

4- The message has to cater for the provision of sending updates (cancellation, replace, provisional, definitive)or new services request as shifts, request for second berth, etc.)

5- The berth management acknowledgment message is a message from the party acting on behalf of the localauthority to the party responsible for requesting the berth.


7/28/2019 140v10

8/59


SEGMENT TABLE - UN/EDIFACT D98B BERMAN MESSAGE

Pos Tag Name S R

0010 UNHMessage header M 1

0020 BGM Beginning of message M 1

0030 DTM Date/time/period C 90040 FTX Free text C 9

0050 RFF Reference C 9

0060 Segment group 1 M 9

0070 NAD Name and address M 1

0080 Segment group 2 C 90090 CTA Contact information M 1

0100 COM Communication contact C 9

0110 Segment group 3 M 99

0120 TDT Details of transport M 1

0130 RFF Reference C 9

0140 DTM Date/time/period C 90150 MEA Measurements C 99

0160 FTX Free text C 9

0170 Segment group 4 C 999

0180 LOC Place/location identification M 10190 DTM Date/time/period C 9


0210 GOR Governmental requirements M 10220 RFF Reference C 9

0230 NAD Name and address C 99


0250 TSR Transport service requirement M 1

0260 LOC Place/location identification M 1

0270 MEA Measurements C 90280 DTM Date/time/period C 9

0290 POC Purpose of conveyance C 9

0300 FTX Free text C 9


0320 HAN Handling instructions M 1

0330 NAD Name and address C 9


0350 GDS Nature od cargo M 90360 FTX Free text C 9

0370 MEA Measurements C 9

0380 EQN Number of unit C 9

0390 DGS Dangerous goods C 9

0400 UNT Message trailer M 1


7/28/2019 140v10

9/59

7/28/2019 140v10

10/59


Coding of Related Locations in the LOC Segment D4/47Maritime Use of the TCC Group D4/48

Inland Transport Use of the TCC Group D4/49 (in preparation)

Compliance with ITIGG Principles and Rules D4/50

Data Definition Above and Below CNI in Multi-Consignment D4/51Messages

Use of the DOC Segment at Various Levels D4/52Use of the UNB Segment D4/53Definition of a Consignment D4/54


7/28/2019 140v10

11/59


INDEX OF SPECIFIC RECOMMENDATIONS

The Index which follows covers the recommendations included in this document.

Two columns have been included showing the status of each segment in the message (UNSM) and the usagerecommended by ITIGG.

The message documentation should be consulted for details of message structure.

BERMAN MESSAGE RECOMMENDATIONS NUMBER UNSM

ITIGG

Header Level UNH D4/1401 M M

BGM D4/1402 M M

DTM D4/1403 C R FTX D4/1404 C O

RFF D4/1405 C O

Party Details D4/1406 M M

NAD D4/1407 M M

Contacts D4/1408 C O

CTA D4/1409 M M

COM D4/1410 C O

Transport Details D4/1411 M M

TDT D4/1412 M MRFF D4/1413 C O

DTM D4/1414 C R

MEA D4/1415 C R FTX D4/1416 C O

Location Information D4/1417 C D

LOC D4/1418 M M

DTM D4/1419 C D

Custom Information D4/1420 C O

GOR D4/1421 M M

RFF D4/1422 C O

NAD D4/1423 C O

Transport Service Details D4/1424 C R

TSR D4/1425 M MLOC D4/1426 M M

MEA D4/1427 C D

DTM D4/1428 C DPOC D4/1429 C R

FTX D4/1430 C O

Cargo Operation D4/1431 C D

HAN D4/1432 M MNAD D4/1433 C O


7/28/2019 140v10

12/59


Goods Item Details D4/1434 C D

GDS D4/1435 M M

FTX D4/1436 C OMEA D4/1437 C D

EQN D4/1438 C DDGS D4/1439 C D

Message Trailer UNT D4/1440 M M


7/28/2019 140v10

13/59


MESSAGE HEADER

RECOMMENDATION D4/1401 - USE OF THE UNH M

FUNCTION OF THE SEGMENT

The UNH segment is used to head, identify and specify a message

MESSAGE REQUIREMENTS

BERMAN Header M 1

RECOMMENDED SEGMENT USAGE

Use of the UNH segment is mandatory.

RECOMMENDED SEGMENT DETAIL

MSG REC ELEMENT DESCRIPTION SIZE/TYPE

M M 0062 MESSAGE REFERENCE NUMBER (unique within an interchange) an..14

M M S009 MESSAGE IDENTIFIER

M M 0065 Message type identifier an..6

BERMAN Berth management

M M 0052 Message type version number an..3

D

M M 0054 Message type release number an..3

98B

M M 0051 Controlling agency an..2

UN

C R 0057 Association assigned code (Agreed identifier for the Guideline) an..6

ITG00

C O 0068 COMMON ACCESS REFERENCE (Additional message reference if required) an..6

C X S010 STATUS OF THE TRANSFER -

SAMPLE SEGMENT USAGE

UNH+0001+BERMAN:D:98B:UN:ITG00

NOTES ON RECOMMENDATION

0057: Following the principle established by SMDG for the BAPLIE message guideline, thefollowing are suggested, though other values are possible (General Recommendation D4/5refers):

SMDG10 = SMDG Version 1.0

INT10 = INTIS Version 1.0SEA10 = SEAGHA Version 1.0

ANZ10 = Australia/New Zealand Version 1.0

CON10 = Concord Version 1.0ISA10 = ISA Version 1.0

LOT10 = UK ECA Version 1.0

For further information see the section on compliance with ITIGG Principles and Rules in theIntroduction to this document (Recommendation D4/50 refers).


7/28/2019 140v10

14/59



7/28/2019 140v10

15/59


RECOMMENDATION D4/1402 - USE OF THE BGM M


The BGM segment is used to specify the type and function of the message.


BERMAN Header M 1


Use of the BGM segment is mandatory.



C R C002 DOCUMENT/MESSAGE NAME

C R 1001 Document/message name, coded an..3

21 Query

[T36] Declaration inward and outward of vessel

[T37] Application for usage of berth or mooring facilities

[T38] Notification of usage of berth or mooring facilities

[T39] Application for vessels entering into port area in night-time

[T40] Application for designation of berthing places[T41] Application for shifting from designated place in port

[T42] Notification of shifting from designated place in port

[T43] Supplemental document of Application for cargo operation of dangerous goods

[T44] Supplemental document of Application for transport of dangerous goods[U01] Pre-announcement of Vessels

[U02] Report of berth allocation

[U03] Request for berth without prior announcement[U04] Request for berth with prior announcement

[U05] Request for shift of berth

C X 1131 Code list qualifier -

C X 3055 Code list responsible agency, coded -C X 1000 Document/message name -

C R C106 DOCUMENT/MESSAGE IDENTIFICATION

C R 1004 Document/message number (Sender's unique reference number) an..35

C X 1056 Version -

C X 1060 Revision number -

C R 1225 MESSAGE FUNCTION, CODED an..3

1 Cancellation

5 Replace

9 Original

13 Request (Second berth request or New services request as shifts)

C X 4343 RESPONSE TYPE, CODED an..3


BGM+BM1+UUUUASSSSSS+9


1001: The Oxford D4 agreed that for consistency this element will always be used, even for single-

function messages.


7/28/2019 140v10

16/59


RECOMMENDATION D4/1403 - USE OF THE DTM AT HEADER LEVEL R


The Header Level DTM is always used to transmit the date of the manifest and optionally any dates/times

which relate to the whole message. It is recommended that whenever times are


BERMAN Header C 9


Use of the Header Level DTM is required.



M M C507 DATE/TIME/PERIOD

M M 2005 Date/time/period qualifier an..3137 Document / message date / time (Message date / time)

C R 2380 Date/time/period (Date/time) an..35

C R 2379 Date/time/period format qualifier an..3

102 CCYYMMDD

203 CCYYMMDDHHMM

303 CCYYMMDDHHMMZZZ


DTM+137:19981202:102


2005: The Oxford JRT meeting agreed that the appropriate required date/time at this level is that

which would normally appear on the message's paper equivalent (ie. the date placed at the topof a letter).

This is not necessarily the "processing date" (which is the time at which the message was

generated) or the "transmission date" (which is the time which the message is actually sent).

In certain applications "processing date" and "message date" may be the same, if a message is

generated for immediate transmission. If, however, a message is generated and stored for aperiod of time before it is batched for transmission, then the two dates/times will differ.

It has thus been agreed that the most appropriate date for use at this level is that which wouldapply in a paper environment - the date/time at which a document would be printed, prior tobeing placed in an envelope for posting.

The "transmission date" always appears automatically in the transmission "envelope". It

equates to the date/time when a paper envelope is actually posted.

2379: The use of century (eg. 19xx, 20xx) has been recommended as a uniform standard for use in all

messages. Where only the date is known, format code 102 should be used.


7/28/2019 140v10

17/59


RECOMMENDATION D4/1404 - USE OF THE FTX SEGMENT AT HEADER LEVEL O


The FTX segment at this level is used to specify a message type name.


BERMAN Header C 9


The FTX segment at this level is optional.


M M 4451 TEXT SUBJECT QUALIFIER an..3

AAI General Information

ACB Additional Information

CHG Change Information

SSR Special service request

SUR Supplier remarksABY Regulatory information

CIP Customs clearance instruction

C X 4453 TEXT FUNCTION, CODED -

C R C107 TEXT REFERENCE

C M 4441 Free text identification an..17

C O 1131 Code list qualifier an..3

C O 3055 Code list responsible agency, coded an..3

C O C108 TEXT LITERAL

M M 4440 Free text an..70

C O 4440 Free text an..70



C O 4440 Free Text an..70

C X 3453 LANGUAGE, CODED (as per ISO 639-1988) an..3


FTX+



7/28/2019 140v10

18/59

7/28/2019 140v10

19/59


NAME & ADDRESS DETAILS

RECOMMENDATION D4/1406 - USE OF THE HEADER LEVEL NAD GROUP M

FUNCTION OF THE GROUP

The NAD Group at Header Level is used to specify parties and party related information applicable to the

whole message.


BERMAN Group 1 (NAD-Group 2) M 9

RECOMMENDED GROUP USAGE

Use of the NAD Group at Header Level is mandatory.


7/28/2019 140v10

20/59


RECOMMENDATION D4/1407 - USE OF THE NAD TRIGGER SEGMENT M

WITHIN THE HEADER LEVEL NAD GROUP


This NAD segment is the trigger segment of the NAD Group at Header Level and is used to specify a party

which applies to the whole message.


BERMAN Group 1 (NAD) M 1


Use of the NAD trigger segment within this group is mandatory.



M M 3035 PARTY QUALIFIER an..3MS Message sender

CA Carrier

CG Carrier's agent

CN Consignee

CV Consignees vessel

CX Consignee's agent

CPE Vessel master

CPF Means of taransport charterer

OV Owner of means of taransport PR Payer

C D C082 PARTY IDENTIFICATION DETAILS

M M 3039 Party id. identification (Company Code) an..35

company codeC O 1131 Code list qualifier an..3

100 Enhanced party ID (for DUNS plus 4 number)160 Party ID (for DUNS, FMC and carrier's codes)

172 Carrier Code167 Tax party identification


7 CEFIC

9 EAN

10 ODETTE

16 DUNS 20 BIC

184 ACOS

87 Assigned by carrier

163 US FMC (US freight forwarders)166 US NMFCA (SCAC)

148 Spanish Custom

151 JP,Japan Custom213 JP, NACCS

[T17] Japanese Ministry of Transport

[U09] Port Gdynia Holding S.A.[U10] Gdansk Port Authority Cot

C D C058 NAME AND ADDRESS (free format)

M M 3124 Name and address line (free text) an..35

C O 3124 Name and address line (free text) an..35




C D C080 PARTY NAME

M M 3036 Party name an..35

C O 3036 Party name an..35




7/28/2019 140v10

21/59



C X 3045 Party name format, coded -

C D C059 STREET

M M 3042 Street and number/p.o. box an..35

C O 3042 Street and number/p.o. box an..35


C D 3164 CITY NAME an..35

C D 3229 COUNTRY SUB-ENTITY IDENTIFICATION (State/Province Code) an..9

C D 3251 POSTCODE IDENTIFICATION (Postcode/Zip Code) an..9

C D 3207 COUNTRY, CODED an..3


NAD+


General: Three different approaches to the presentation of NAD details are allowed for above:

(a) Coded (C082)(b) Unstructured free text (C058)

(c) Structured free text (C080-C059,3164,3229,3251,3207)

In commercial messages it is unlikely that coded or structured Name and Address will findextensive use in the foreseeable future beyond certain highly sophisticated trading

relationships at a local level.

For the foreseeable future there will be a continuing need to operate "hybrid" systems which

may require data to be printed onto traditional documents at some point of the transport chain.

This is particularly the case where Bills of Lading are to be used in the trade, since a paper Billmust be printed according to Letter of Credit requirements which may not take account of theprecise data structure of an electronic message.

It is therefore likely that the following phased scenario will emerge:

unstructured free text will be used in traditional relationships while electronic trading is

introduced and wherever paper Bills of Lading will be required (the majority of cases

for the foreseeable future)

structured free text will be used in "hybrid" situations where parties have agreed to

refine data requirements, and have resolved problems with Letters of Credit, but still

require detailed identification of a party beyond that which can be established using acompany code

codes will be used in close, established trading relationships where trade proceeds on

the basis of Waybills and highly integrated electronic trading systems


7/28/2019 140v10

22/59


PARTY CONTACTS

RECOMMENDATION D4/1408 - USE OF THE CTA GROUP O



The CTA Group within the NAD Group at Header Level is used to specify contact details for the party

specified in the preceding NAD segment.


BERMAN Group 2 (NAD-CTA) C 9


Use of the CTA Group at this level is optional.


7/28/2019 140v10

23/59


RECOMMENDATION D4/1409 - USE OF THE CTA TRIGGER SEGMENT M

WITHIN THE CTA GROUP



This CTA segment is the trigger segment of the CTA Group and is used to specify contact information forthe party specified in the preceding NAD segment.


BERMAN Group 2 (NAD-CTA) M 1


Use of the CTA trigger segment within this group is mandatory, if the NAD-CTA Group is used.



C O 3139 CONTACT FUNCTION, CODED an..3

IC Information Contact

C O C056 DEPARTMENT OR EMPLOYEE DETAILS

C X 3413 Department or employee identification -

C R 3412 Department or employee (name) an..35

Contact person name


CTA+IC+:JANE EDMUNDS



7/28/2019 140v10

24/59


RECOMMENDATION D4/1410 - USE OF THE COM SEGMENT O

WITHIN THE CTA GROUP



The COM segment at this level is used to specify communication numbers of the contact identified in thepreceding CTA segment.


BERMAN Group 2 (CTA-COM) C 9


Use of the COM segment within this group is optional



M M C076 COMMUNICATION CONTACT

M M 3148 Communication number (no spaces or hyphens) an..512

communication numberM M 3155 Communication channel qualifier an..3

E1 EDI transmission

EM Electronic mailFX Telefax

TE Telephone

TL Telex

XF X.400


COM+81453367127:TE


General: General Recommendation D4/16 stipulates that communication numbers are to be transmitted

without spaces or hyphens. Telephone and fax numbers should include country codes.


7/28/2019 140v10

25/59


TRANSPORT DETAILS

RECOMMENDATION D4/1411 - USE OF THE HEADER LEVEL TDT GROUP M


The TDT Group in this message is used to specify transport details which apply to the whole message.


BERMAN Group 3 (TDT) M 99


The use of the TDT Group at this level is mandatory.


7/28/2019 140v10

26/59


RECOMMENDATION D4/1412 - USE OF THE TDT TRIGGER SEGMENT M

WITHIN THE HEADER LEVEL TDT GROUP


This TDT segment is the trigger segment of the TDT Group and at this level is used to provide details of

the arriving means of transport.


BERMAN Group 3 (TDT) M 1


Use of the TDT trigger segment within this group is mandatory.



M M 8051 TRANSPORT STAGE QUALIFIER an..320 Main Carriage

C D 8028 CONVEYANCE REFERENCE NUMBER an..17

Voyage Number

C R C220 MODE OF TRANSPORT

C R 8067 Mode of transport, coded an..3

1 Maritime

C X 8066 Mode of transport (text) -

C O C228 TRANSPORT MEANS

C O 8179 Type of means of transport identification an..8

2 Coaster chemical tanker

3 Dry bulk carrier

4 Deep sea chemical tanker

8 Semi container carrier

11 Ship

12 Tanker

[T69] Passenger vessel

[T70] Cargo and Passenger vessel

[T71] General cargo vessel

[T72] Crude Oil tanker

[T73] Liquefied petroleum gas (LPG) carrier

[T74] Liquefied natural gas (LNG) carrier

[T78] Product oil tanker

[T79] Grain carrier

[T80] Timber or logs carrier

[T82] Wood chips carrier

[T83] Steel product vessel [T84] Gravel vessel

[T85] Cement r vessel [T86] Coal vessel

[T87] Ore carrier

[T88] Pure Car carrier

[T89] War ship

[T90] Container only vessel

[T92] Roll on/Roll-off vessel

[T93] Ferry vessel

[T94] Fishing vessel

[T95] Work vessel

[T96] Patrol vessel

[T97] Tug boat or push boat

[T98] Supply ship[U14] Training vessel

C O 8178 Type of means of transport an..17


7/28/2019 140v10

27/59


C D C040 CARRIER

C O 3127 Carrier identification (Port system agent code or carrier code) an..17C O 1131 Code list qualifier an..3

172 Carrier Code

ZZZ Mutually agreed


16 DUNS 20 BIC


166 US NMFCA (SCAC)

184 Australian Chamber of Shipping 213 JP,NACCS

ZZZ Mutually agreed

[U09] Port Gdynia Holding S.A.

[U10] Gdansk Port Authority Co

C O 3128 Carrier name (free text)

carrier name

C X 8101 TRANSIT DIRECTION, CODED -

C X C401 EXCESS TRANSPORTATION INFORMATION

C R C222 TRANSPORT IDENTIFICATION

C D 8213 Id. of means of transport identification an..9

Call Sign

Lloyd's Number

official number


103 Call Sign Directory (8213 = Call Sign)

146 Transport ID (8213 Call Sign )


11 Lloyds register of shipping (8213=Lloyds Number)

[T17] Ministry of transport, Japan (8213= official number)

[U09] Port Gdynia Holding S.A. (8213= official number)

[U10] Gdansk Port Authority Co (8213= official number)

C O 8212 Id. of means of transport an..35

Vessel name (or other means of transport ID free text)

C O 8453 Nationality of means of transport, coded an..3

Use ISO 3166

C X 8281 TRANSPORT OWNERSHIP, CODED an..3


TDT+20+100017+1++NLL:172:166:Nedlloyd+++9001253:146::NEDLLOYD HONG KONG



7/28/2019 140v10

28/59


RECOMMENDATION D4/1413 - USE OF THE RFF SEGMENT O



This RFF segment is used to specify a reference which applies to the stage or means of transport specified

in the preceding TDT segments.


BERMAN Group 3 (TDT) C 9


Use of the RFF segment within this group is optional.



C O C506 REFERENCEM M 1153 Reference qualifier an..3

VM Vessel identification

ZL Shipping line identificationPR Price quote number

IT Internal customer number

SF Ship from

[U13] Ex vessel name

C R 1154 Reference number an..35

" Lloyds number"

Shipping line reference numberConference number

Internal customer number

Port of registry

Ex vessel name

C X 1156 Line number -

C X 4000 reference version number -


RFF+



7/28/2019 140v10

29/59


RECOMMENDATION D4/1414 - USE OF THE DTM SEGMENT R



The DTM segment at this level is used to specify dates and times which relate to means of transport

specified in the preceding TDT segments.


BERMAN Group 4 (TDT-LOC) C 9


The DTM segment at this level is required.



M M C507 DATE/TIME/PERIODM M 2005 Date/time/period qualifier an..3

132 Arrival date/time, estimated

133 Departure date/time, estimated 178 Arrival date/time, actual

186 Departure date/time, actual



102 CCYYMMDD

203 CCYYMMDDHHMM 303 CCYYMMDDHHMMZZZ


DTM+132:19961205:102




The use of 303 (CCYYMMDDHHMMZZZ) is to be preferred over 203

(CCYYMMDDHHMM) - (General Recommendation D4/23 refers).


7/28/2019 140v10

30/59


RECOMMENDATION D4/1415 - USE OF THE MEA SEGMENT R



The MEA segment at this level is used to specify any measurements other than dimensions which relate to

the means of transport specified in the preceding TDT.




Use of the MEA segment within this group is required.



M M 6311 MEASUREMENT APPLICATION QUALIFIER an..3AAE Measurement

AAN Weight of conveyance

AAO Convenience summer dead weightLAO Vessel overall length

ABS Velocity

C O C502 MEASUREMENT DETAILS

C R 6313 Measurement dimension, coded an..3

AAM Gross tonnage of vessel

AAN Net tonnage of vessel

ACG Chargable weight

HM Height, maximum

LM Length, maximumWM Width, maximum

[T45] Bow and bridge distance (BTB)

C X 6321 Measurement significance, coded -

C X 6155 Measurement attribute, code -

C X 6154 Measurement attribute -

C R C174 VALUE/RANGE

M M 6411 Measure unit qualifier an..3

TNE Tons

KGM KilogramsMTR Metres

KNT Knot

C R 6314 Measurement value (Weight or volume) n..18

C X 6162 Range minimum -

C X 6152 Range maximum -

C X 7383 SURFACE/LAYER INDICATOR, CODED -


MEA+AAE+AAM+TNE:3000

MEA+LAO++MTR:200



7/28/2019 140v10

31/59


RECOMMENDATION D4/1416 - USE OF THE FTX SEGMENT O



The FTX segment at this level is used to specify any other information which related to the means of

transport specified the preceding TDT segment.






M R 4451 TEXT SUBJECT QUALIFIER an..3



C D C107 TEXT REFERENCE an..17

C M 4441 Free text identification an..17









C O 3453 LANGUAGE, CODED (as per ISO 639-1988) an..3


FTX+



7/28/2019 140v10

32/59


Location Information

RECOMMENDATION D4/1417 - USE OF THE LOC GROUP D



The LOC Group within the TDT Group at Header Level is used to specify the loaction related to the

means of transport specified the preceding TDT segment.




Use of the LOC Group at this level is Dependent.


7/28/2019 140v10

33/59


RECOMMENDATION D4/1418 - USE OF THE LOC TRIGGER SEGMENT M

WITHIN THE LOC GROUP



This LOC segment is used to specify locations which relate to the stage and means of transport specified inthe preceding TDT segment.


BERMAN Group 4 (TDT-LOC) M 1


Use of the LOC trigger segment within this group is mandatory.



M M 3227 PLACE/LOCATION QUALIFIER an..3

5 Place of depature

94 Previous of port of call

61 Next port of call

125 Last port of call 89 Place of registration

9 Place / port of loading

11 Place / port of discharge160 Foreign port of call

153 Port of call

61 Next port of call

C R C517 LOCATION IDENTIFICATION

C A 3225 Place/location identification an..25

UN LOCODE


139 Place/port

ZZZ Mutually agreed


6 UN/ECE

ZZZ Mutually Agreed

C O 3224 Place/location (free text) an..70

C X C519 RELATED LOCATION ONE IDENTIFICATION -

C X C553 RELATED LOCATION TWO IDENTIFICATION -

C X 5479 RELATION, CODED -


LOC+125+JPTYO:139:6


3225: Use of the UN LOCODE is preferred for international maritime carriage.

3227: The port of loading should only be used when the message is to notify cancellation of a

voyage call


7/28/2019 140v10

34/59


RECOMMENDATION D4/1419 - USE OF THE DTM SEGMENT D

WITHIN THE LOC GROUP



The DTM segment at this level is used to specify dates and times which relate to loaction andt the means oftransport specified in the preceding LOC segment.




The DTM segment at this level is dependent.



M M C507 DATE/TIME/PERIOD

M M 2005 Date/time/period qualifier an..3

132 Arrival date/time, estimated

133 Departure date/time, estimated

178 Arrival date/time, actual

186 Departure date/time, actual



102 CCYYMMDD

203 CCYYMMDDHHMM

303 CCYYMMDDHHMMZZZ


DTM+132:19961205:102


General: The DTM at this level may be used to specify the estimated date/time of arrival when specifiedin the preceding LOC segment.

The dates are operational rather than contractual.



The use of 303 (CCYYMMDDHHMMZZZ) is to be preferred over 203

(CCYYMMDDHHMM) - (General Recommendation D4/23 refers).


7/28/2019 140v10

35/59


CUSTOM INFORMATION

RECOMMENDATION D4/1420 - USE OF THE GOR GROUP O



The GOR Group is used to provide customs information.


BERMAN Group 5 (GOR) C 9


Use of the GOR Group is optional.


7/28/2019 140v10

36/59

7/28/2019 140v10

37/59


RECOMMENDATION D4/1422 -USE OF THE RFF SEGMENT O

WITHIN THE GOR GROUP



This RFF segment is used to specify a reference which applies to customs refference codes .




Use of the RFF segment within this group is optional.



C O C506 REFERENCEM M 1153 Reference qualifier an..3

AEM Transport route

AFM Secondary Customs refference

C R 1154 Reference number an..35

Regular Shipping line

Simplified transit procedures

C X 1156 Line number -

C X 4000 reference version number -


RFF+AEM:1357



7/28/2019 140v10

38/59


RECOMMENDATION D4/1423 - USE OF THE NAD SEGMENT O

WITHIN THE GOR GROUP



This NAD segment is used to identify the consortia menbers sharing a vessel.




Use of the NAD segment within this group is optional.



M M 3035 PARTY QUALIFIER an..3CX Consignee's agent

C D C082 PARTY IDENTIFICATION DETAILS


company codeC O 1131 Code list qualifier an..3

167 Tax party identification


148 Spanish Custom





C O 3124 Name and address line (free text) an..35C O 3124 Name and address line (free text) an..35

C D C080 PARTY NAME







C D C059 STREET




C D 3164 CITY NAME an..35

C D 3229 COUNTRY SUB-ENTITY IDENTIFICATION (State/Province Code) an..9

C D 3251 POSTCODE IDENTIFICATION (Postcode/Zip Code) an..9

C D 3207 COUNTRY, CODED an..3


NAD+CX+323:167:148+Bilbo shipping



7/28/2019 140v10

39/59


TRANSPORT SERVICE DETAILS

RECOMMENDATION D4/1424 - USE OF THE HEADER LEVEL TSR GROUP R


The TSR Group is used to specify details for the transport service requirements.


BERMAN Group 6 (TSR) C 9


Use of the TSR Group is required.


7/28/2019 140v10

40/59


RECOMMENDATION D4/1425 - USE OF THE HEADER LEVEL TSR TRIGGER SEGMENT M

WITHIN THE HEADER LEVEL TSR GROUP


The TSR is used to identify the contract, conditions of carriage, services and priority requirements which

apply to the transport of the whole consignment.


BERMAN Group 6 (TSR) M 1


Use of the TSR trigger segment within this group is mandatory.



C O C536 CONTRACT & CARRIAGE CONDITION

M M 4065 Contract & carriage condition, coded an..3

9 Ordinary

4 Combined transport (intermodal contracts)14 Through transport



C R C233 SERVICE

M M 7273 Service requirement, coded (origin) an..3

38 Request for administration service

C X 1131 Code list qualifier

C X 3055 Code list responsible agency, coded

C X 7273 Service requirement, coded (destination) an..3


C X 3055 Code list responsible agency, coded

C X C537 TRANSPORT PRIORITY 4219 Transport priority, coded an..3


C X 3055 Code list responsible agency, coded -

C X C703 NATURE OF CARGO

M M 7085 Nature of cargo, coded (see note below) an..3




TSR+9+38

NOTES ON RECOMMENDATION D4/307


7/28/2019 140v10

41/59


RECOMMENDATION D4/1426 - USE OF THE LOC SEGMENT M



This LOC segment is used to specify locations which relate to the the transport service requirements

specified the preceding TSR segment.


BERMAN Group 6 (TSR) C9


Use of the LOC(MEA) segment within this group is mandatory.



M M 3227 PLACE/LOCATION QUALIFIER an..39 Place/port of loading (Operational port of loading)

11 Place/port of discharge (Operational port of discharge)

60 Place of arrival

164 Berth

[T14] Previous Berth[T15] Next Berth

C R C517 LOCATION IDENTIFICATION

C A 3225 Place/location identification an..25

UN LOCODE


139 Place/port


6 UN/ECE

C O 3224 Place/location (free text) an..70

C R C519 RELATED LOCATION ONE IDENTIFICATION

C R 3223 Related place/location one identification (1st related location code) an..25

Berth code etc.


[BER] Berths

[WHA] Wharves

[TER] Terminals

[STO] Storage facilities[REP] Repair facilities

[POL] Pilot station

[U06] Other location in the port authority area


9 EAN

184 ACOS

[T17] Ministry of transport, Japan


[U10] Gdansk Port Authority Cot

ZZZ Mutually Agreed

C O 3222 Related place/location one (1st related location free text) an..70


7/28/2019 140v10

42/59


C O C553 RELATED LOCATION TWO IDENTIFICATION

C O 3233 Related place/location two identification (2nd related location code) an..25C O 1131 Code list qualifier an..3

[BER] Berths

[WHA] Wharves

[TER] Terminals[STO] Storage facilities

[REP] Repair facilities

[POL] Pilot stationC O 3055 Code list responsible agency, coded an..3

9 EAN

184 ACOS

[214] Ministry of transport, Japan

ZZZ Mutually Agreed

C O 3232 Related place/location two (2nd related location free text) an..70

C X 5479 RELATION, CODED -


LOC+9+JPTYO:139:6+HK001:[BER]:9


3225: Use of the UN LOCODE is preferred for international maritime carriage.

3227: The port of loading should only be used when the message is to notify cancellation of a

voyage call


7/28/2019 140v10

43/59


RECOMMENDATION D4/1427 - USE OF THE MEA SEGMENT D



The MEA segment at this level is used to specify any measurements other than dimensions which relate to

the relate to the the transport service requirements specified the preceding TSR segment.




Use of the MEA segment within this group is dependent.



M M 6311 MEASUREMENT APPLICATION QUALIFIER an..3AAE Measurement



AEQ Forward draft

AER After draft




C R C174 VALUE/RANGE

M M 6411 Measure unit qualifier an..3

MTR Metres

C R 6314 Measurement value (Weight or volume) n..18





MEA+AAE+AEQ+MTR:14



7/28/2019 140v10

44/59


RECOMMENDATION D4/1428 - USE OF THE DTM SEGMENT D



The DTM segment at this level is used to specify dates and times which relate to the the transport service

requirements specified the preceding TSR segment.




The DTM segment at this level is dependent.



M M C507 DATE/TIME/PERIODM M 2005 Date/time/period qualifier an..3

178 Arrival date/time, actual

186 Departure date/time, actual 132 Arrival date/time, estimated

133 Departure date/time, estimated

C R 2380 Date/time/period (Date/time) an..35C R 2379 Date/time/period format qualifier an..3

102 CCYYMMDD

203 CCYYMMDDHHMM

303 CCYYMMDDHHMMZZZ


DTM+178:199812050800:203


General: The DTM at this level may be used to specify the estimated date/time of arrival when specified

in the preceding LOC segment.

The dates are operational rather than contractual.



The use of 303 (CCYYMMDDHHMMZZZ) is to be preferred over 203(CCYYMMDDHHMM) - (General Recommendation D4/23 refers).


7/28/2019 140v10

45/59


RECOMMENDATION D4/1429 - USE OF THE POC SEGMENT R



The POC segment at this level is used to specify the purpose of conveyance call information related to

service specified in the preceding TSR segment.




The POC segment at this level is requiered.


M M C525 PURPOSE OF CONVEYANCE CALL

C R 8025 Purpose of conveyance call, coded an..3

1 Cargo operation

2 Passenger movement

3 Taking bunkers4 Changing crew

5 Goodwill visit

6 Taking supplies

7 Repair 8 Laid-up

9 Awaiting orders

10 Miscellaneous[T46] Crew movement

[T47] Cruise, leisure and recreation[T48] Under goverment order

[T49] Quarantine inspection

[T68] Refuge

C X 1131 Code list qualifier an..3C X 3055 Code list responsible agency, coded an..3

C X 8024 Purpose of conveyance call an..35


POC+1



7/28/2019 140v10

46/59





The FTX segment at this level is used to specify any other information related to service specified in the

preceding TSR segment.








AAC Dangerous goods additional information

ADU Note


C O C107 TEXT REFERENCE

M M 4441 Free text identification an..17











FTX+



7/28/2019 140v10

47/59


CARGO OPERATION

RECOMMENDATION D4/1431 - USE OF THE HAN GROUP D



The HAN Group at this level is used to specify details for the cargo operations to be carried out.


BERMAN Group 7 (TSR-HAN) C 9


The HAN Group at this level is dependent. It is not used if there is no cargo operation, otherwise it isrequired.


7/28/2019 140v10

48/59


RECOMMENDATION D4/1432 - USE OF THE HAN SEGMENT M

WITHIN THE HAN GROUP



The HAN segment at this level is used to specify handling instructions which relate to the goods itemidentified in the preceding GID segment.


BERMAN Group 7 (TSR-HAN) M 1


The HAN trigger segment within this group is mandatory.


C R C524 HANDLING INSTRUCTIONS CC O 4079 Handling instructions, coded C an..3

Coded handling instructions

[LLO] Loading

[LDI] Discharge

[RES] Re-stow

[T] Transit

[TSP] Transportation within the same port

[CTC] Cargo tank cleaning

[CUS] Custom declaration only

[BUN] Bunkering only

[DRY] Repairs in dry-dock

[WET] Repairs in wet-dock

[NO] No cargo operation

C X 1131 Code list qualifier an..3C D 3055 Code list responsible agency, coded an..3

9 EAN

184 ACOS

[T17] Japanese Ministry of Transport


[U10] Gdansk Port Authority Cot

ZZZ Mutually Agreed

C X 4078 Handling instructions an..70

C X C218 HAZARDOUS MATERIAL

C X 7419 Hazardous material class code, identification an..4

C X 1131 Code list qualifier an..3

C X 3055 Code list responsible agency, coded an..3

C X 7418 Hazardous material class an..35


HAN+1::9



7/28/2019 140v10

49/59


RECOMMENDATION D4/1433 - USE OF THE NAD SEGMENT O




This NAD segment at this level this is used to specify a party which applies to the consignment identifiedin the previous HAN segment.


BERMAN Group 7 (TSR-HAN) C 9


Use of the NAD trigger segment within this group is optional.



M M 3035 PARTY QUALIFIER an..3

CA Carrier

CG Carrier's agent

TR Terminal operator

C O C082 PARTY IDENTIFICATION DETAILS


company code


100 Enhanced party ID (for DUNS plus 4 number)

160 Party ID (for DUNS, FMC and carrier's codes)172 Carrier Code


7 CEFIC

9 EAN

10 ODETTE

16 DUNS

20 BIC 184 ACOS


163 US FMC (US freight forwarders)

166 US NMFCA (SCAC)







C D C080 PARTY NAME







C O C059 STREET




C O 3164 CITY NAME an..35

C O 3229 COUNTRY SUB-ENTITY IDENTIFICATION (State/Province Code) an..9


7/28/2019 140v10

50/59


C O 3251 POSTCODE IDENTIFICATION (Postcode/Zip Code) an..9

C O 3207 COUNTRY, CODED an..3


NAD+TR:xxxxxxxx:160:16++BROWN LTD


General: Three different approaches to the presentation of NAD details are allowed for above:

(a) Coded (C082)

(b) Unstructured free text (C058)(c) Structured free text (C080-C059,3164,3229,3251,3207)

In commercial messages it is unlikely that coded or structured Name and Address will find

extensive use in the foreseeable future beyond certain highly sophisticated tradingrelationships at a local level.

For the foreseeable future there will be a continuing need to operate "hybrid" systems whichmay require data to be printed onto traditional documents at some point of the transport chain.

This is particularly the case where Bills of Lading are to be used in the trade, since a paper Bill

must be printed according to Letter of Credit requirements which may not take account of the

precise data structure of an electronic message.

It is therefore likely that the following phased scenario will emerge:

unstructured free text will be used in traditional relationships while electronic trading is

introduced and wherever paper Bills of Lading will be required (the majority of cases

for the foreseeable future)

structured free text will be used in "hybrid" situations where parties have agreed to

refine data requirements, and have resolved problems with Letters of Credit, but still

require detailed identification of a party beyond that which can be established using a

company code

codes will be used in close, established trading relationships where trade proceeds on

the basis of Waybills and highly integrated electronic trading systems


7/28/2019 140v10

51/59


GOODS ITEM DETAILS

RECOMMENDATION D4/1434 - USE OF THE GDS GROUP D




The GDS Group at this level is used to specify goods which are applicable to the onward carriagespecified in the preceding TSR segment.


BERMAN Group 8 (TSR -HAN- GDS) C 9


Use of the GDS Group at this level is dependent.


7/28/2019 140v10

52/59


RECOMMENDATION D4/1435 - USE OF THE GDS TRIGGER SEGMENT M

WITHIN THE GDS GROUP




The GDS segment at this level is used to specify the nature of the goods item identified in the preceding

HAN segment.


BERMAN Group 8 (TSR -HAN- GDS) M 9


Use of the GDS trigger segment within this group is mandatory.



C R C703 NATURE OF CARGO

M M 7085 Nature of cargo, coded an..3

[U12] Waste

5 Other non-containerised

6 Vehicles

7 Roll-on roll-off

8 Palletised 9 Containerised

10 Breakbulk

11 Hazardous cargo

12 General cargo13 Liquid cargo

14 Temperature controlled cargo

15 Environmental pollutant cargo16 Not-hazardous cargo

C D 1131 Code list qualifier an..3

[U11] Commodity class

130 Special handling indication

C D 3055 Code list responsible agency, coded

6 UN/ECE


GDS+12:161:6

NOTES ON RECOMMENDATION D4/400

General: The GDS segment may be repeated to provide any of the following high-level characteristics

of a cargo item for either statistical or operational purposes:

a) the statistical classification of the nature of the goods item by means of specifying the first 2

digits of the Harmonised System code in DE 7085.b) the type of cargo (e.g. RORO or containerised etc.) by specifying one of the DE 7085 codes

5,6,7,8,9,10,11 or 12 from the list below or a 2 digit type of cargo code from UN/ECE

Recommendation no 21.c) any special handling indications (e.g. Hazardous, out of gauge etc.) by specifying one of the

DE 7085 codes 13,14,15 or 16 from the list below.

7085: Recommended code values are as follows:

5 Other non-containerised6 Vehicles

7 Roll-on roll-off


7/28/2019 140v10

53/59


8 Palletised9 Containerised

10 Breakbulk

11 Hazardous cargo

12 General cargo13 Liquid cargo

14 Temperature controlled cargo15 Environmental pollutant cargo16 Not-hazardous cargo

1131/3055: These codes should be used to specify the type of high-level information being specified

except when the dummy value XX is used in DE7085 in which case they are not used.


7/28/2019 140v10

54/59







The FTX segment at this level is used to specify any other information about cargo (e.g. cargo name)

identified in the preceding GDS segment, if the cargo is bulky.


BERMAN Group 8 (TSR-HAN-GDS) C 9


Use of the FTX at this level is optional.






C X C107 TEXT REFERENCE -

C X 1131 Code list qualifier -


C R C108 TEXT LITERAL


cargo name







FTX+ACB+++cargo name



7/28/2019 140v10

55/59


RECOMMENDATION D4/1437- USE OF THE MEA SEGMENT D





The MEA segment at this level is used to specify any measurements other than dimensions which relate tothe cargo identified in the preceding GDS segment.




Use of the MEA segment within this group is dependent.



M M 6311 MEASUREMENT APPLICATION QUALIFIER an..3

AAE Measurment



AAW Gross volume

AAL Actual net weightABJ Volume

G Gross weight

WT Weight




C R C174 VALUE/RANGEM M 6411 Measure unit qualifier an..3

TNE Tones

KGM Kilograms

MTQ Cubic meter

C R 6314 Measurement value n..18

Weight or volume





MEA+AAE+G+TNE:14



7/28/2019 140v10

56/59


RECOMMENDATION D4/1438 - USE OF THE EQN SEGMENT D





The EQN segment at this level is used to specify the number of packages (despatch units)within the goods

item to the measurement specified in the preceding GDS.

.MESSAGE REQUIREMENTS



Use of the EQN segment within this group is dependent.



M M C523 NUMBER OF UNIT DETAILS

C R 6350 Number of units n..15

C X 6353 Number of units qualifier -


EQN+10



7/28/2019 140v10

57/59


RECOMMENDATION D4/1439 - USE OF THE DGS SEGMENT D





This DGS segment is used to specify any dangerous goods details for the goods item specified in the

preceding GDS segment.




Use of the DGS segment within this group is dependent.



C R 8273 DANDEROUS GOODS REGULATIONS, CODED an..3

[ADN] Inland Waterways DG Book (ADNR)

ADR European Road Transport Agreement for DG

CFR CFR49 Code for US domestic transportation

ICA IATA ICAO

IMD IMDG CodeRID Rail/Road DG Book

[JPD] Japanese Dangerous Goods Code

C R C205 HAZARD CODE

M M 8351 Hazard code identification an..7

IMDG Class Number

IMDG Sub-Class NumberRID Class Number

CFR49 codesC O 8078 Hazard substance/item/page number(IMDG Code Page Number) an..7

C O 8092 Hazard code version number(IMDG Code Version Number) an..10

C O C234 UNDG INFORMATION

C R 7124 UNDG number n4

C X 7088 Dangerous goods flashpoint -

C D C223 DANGEROUS GOODS SHIPMENT FLASHPOINT

C R 7106 Shipment flashpoint n3

C R 6411 Measure unit qualifier an..3

CEL Celsius

FAH Fahrenheit

C O 8339 PACKING GROUP, CODED an..3

1 Great danger (= I)

2 Medium danger (= II)

3 Minor danger (= III)

C O 8364 EMS NUMBER an..6

C O 8410 MFAG an..4

C O 8126 TREM CARD NUMBER an..10

C O C235 HAZARD IDENTIFICATION

C O 8158 Hazard identification number, upper part an..4

C O 8186 Substance identification number, lower part an4

C O C236 DANGEROUS GOODS LABEL

C R 8246 Dangerous goods label marking an..4C O 8246 Dangerous goods label marking an..4

C O 8246 Dangerous goods label marking an..4


7/28/2019 140v10

58/59


C O 8255 PACKING INSTRUCTION, CODED an..3

C X 8325 CATEGORY OF MEANS OF TRANSPORT, CODED -

C X 8211 PERMISSION FOR TRANSPORT, CODED -


DGS+


General: The recommendations applying to the DGS Group should be applied wherever the DGS is

used in a variety of messages, both Commercial and Operational. D4 Recommendation 17

refers.

8351: For goods with a subsidiary risk code, two methodologies are currently being applied:

(a) the DGS segment should be repeated using DE 8273 and DE 8351 only

(b) subsidiary risk should be shown in the FTX segment

7124: DE 7124 must be sent if C234 is used.

7106: Flashpoint temperatures should be stated to one decimal place.


7/28/2019 140v10

59/59


RECOMMENDATION D4/1440 - USE OF THE UNT SEGMENT M


The UNT segment is used to end, identify and specify the number of segments in a message


BERMAN Trailer M 1


Use of the UNT segment is mandatory.



M M 0074 NUMBER OF SEGMENTS IN THE MESSAGE n..6

M M 0062 MESSAGE REFERENCE NUMBER (Should match 0062 in the UNH) an..14


UNT+40+128


Date post:	03-Apr-2018
Category:	Documents
Upload:	ksenthil77
View:	219 times
Download:	1 times

140v10

Documents