Zim Codeco
Zim Codeco
FOR THE
IMPLEMENTATION OF
TRANSPORT EDI MESSAGES
CODECO
GATE ACTIVITY MESSAGE
GENERAL INTRODUCTION
INTERNATIONAL TRANSPORT IMPLEMENTATION GUIDELINES GROUP 2
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 the recommended usage of codes, qualifiers, data elements, composites, segments and groups of
segments in the D95B CODECO message.
This document has been developed as part of a set of reference guidelines for the following maritime-
related container messages:
The intention is to provide guidance to developers to ensure consistent use throughout the worldwide
trade and transport community.
By establishing this consistency, trade and transport organisations and their supporting software
developers and 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 JM4/ITIGG/105 which refers to document number 105 issued by
UN/EDIFACT Joint Message Development Group 4 (Transport), through its International Transport
Implementation Guidelines Sub-Group.
RELATED DOCUMENTS
The general introduction to usage of the Container Message set, entitled “Guide to the UN/EDIFACT
Container Handling Messages” (Guide to the Scenario of EDIFACT Container Messages), document
number JM4/ITIGG/102. The purpose of that document is to outline for users, the use and
interrelationship between the various UN/EDIFACT container handling messages developed by the
JM 4 Group.
The document entitled Principles and Rules for the Implementation of Transport EDI Messages -
Transport Equipment Movements”, number JM4/ITIGG/101. This document provides a complete set
of detailed and annotated recommendations on usage of each segment in the container message set.
This document is based on the UN/EDIFACT D95B directory. This directory has been designated by
JM4 (Transport) as the basis for all global implementations and associated guidelines for the Container
Message set. A review of this document will be undertaken during late 1997/early 1998.
At its Helsinki meeting in September 1996, JM4/ITIGG agreed on specific conditions for compliance
with the Principles and Rules laid out in this document. These conditions take the form of
Recommendation JM4/50, which reads as follows:
JM4 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 JM4 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:
1.2 The General Recommendations approved by JM4 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 an
Implementation 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 JM4/5.
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
and approved 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
differing interpretations 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 (JM4) 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 JM4 (Transport) formed an informal group to
attempt to harmonise known 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 of 1996 which would provide the principles and rules for the international implementation of
electronic messages in 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 JM4
(Transport) work group decided to recognise ITIGG as the source of guideline harmonisation information
and leadership. JM4 also took a decision to officially accept ITIGG as a sub-group of JM4 (Transport).
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 usage
between different industry sectors. This has received the endorsement of other key working groups
within UN/EDIFACT.
This formal working group (known as T8) met for the first time at the Singapore JRT meeting in April
1997, and has commenced the task of comparing the usage of common segments by different industry
sectors.
Status Indicators
Status Indicators (M and C) form part of the UN/EDIFACT standard and indicate a minimum
requirement to fulfil the needs of the message structure.
Value Description
M Mandatory
This entity must appear in all messages. Shown as Usage Indicator "M" in
Implementation Guidelines.
C Conditional
A 'Conditional' Status Indicator may be represented by a supporting Usage Indicator which is either R,
O, D or X (see below)
Usage Indicators
Throughout this document reference is made to indicators (M, R, D, O and X) which are shown adjacent
to data 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
R 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.
X Not Used
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.
Any differences of substance between this version of the document and the previous version have been
identified in the text with a line in the left margin.
* Introduction
* Segment Table
* UNH
* BGM
* TDT (Group 1)
* RFF (Group 1)
* EQD (Group 5)
* RFF (Group 5)
* DTM (Group 5)
* TMP (Group 5)
* RNG (Group 5)
* SEL (Group 5)
* EQA (Group 5)
* LOC (Group 7)
* NAD (Group 6)
Requests for further changes can be lodged with the secretariat using a form on the ITIGG web site (see
below).
DOCUMENT MAINTENANCE
The data content of this document has been prepared and approved by UN/EDIFACT JM4/ITIGG and no
alteration may be made to the content of this document without reference to and approval of JM4/ITIGG.
Any remarks, questions, amendments or requested alterations to this document are to be addressed to:-
ITIGG Secretariat
c/- Karl Zlotkowski
Tradegate Australia Ltd
Suite 1606, Level 16, 44 Market Street
Sydney NSW 2000 AUSTRALIA
preferably via the UN/EDIFACT Transport Work Group / Message Design Group in the requestor's
region.
“A message by which a terminal, depot, etc. confirms that the containers specified have been delivered or
picked up by the inland carrier (road, rail or barge).
“This message can also be used to report internal terminal container movements (excluding loading and
discharging the vessel).
“This message is part of a total set of container-related messages. These messages serve to facilitate the
intermodal handling of containers by streamlining the information exchange. The business scenario for the
container messages is clarified in a separate document, called: 'Guide to the scenario of EDIFACT
container messages'.”
The ‘Guide to the scenario of the EDIFACT container messages’ has been published by ITIGG under the
title “Guide to the UN/EDIFACT Container Messages” (Document reference JM4/ITIGG/96.103).
CLARIFICATION
The CODECO message is intended for the reporting of gate activity (gate movements) associated with an
item of equipment in and out of a container terminal, storage and repair facility, or packing/unpacking
facility.
It can also be used to report movements within the facility, including changes to the status of the item of
equipment after servicing or repair.
The container leasing industry will also use it for notification of changes to the lease status of a container -
ie. as a report of on/off hire or direct interchange.
The message is intended for the provision of operational reports, which may be used for the updating of
equipment tracking systems. It is not intended as a primary source of commercial information, which is
better provided in commercial messages such as the IFTM Set which are exchanged between parties directly
associated with commercial (cargo-related) transactions.
This Guideline does, however, provide for the transmission of operational information which will
compliment commercial systems and interact seamlessly with EDIFACT commercial messages.
At its April 1997 meeting in Singapore JM4 agreed that the functionality of messages in the Container
Message set could be extended to cover break-bulk or non-containerised cargo in situations where both
types of cargo are handled in the same operation, and where this could be supported by the particular
message. Wording to this effect has been inserted in the “Guide to the UN/EDIFACT Container Messages”.
The effect of this decision is to extend the use of CODECO to potentially cover all cargo movements, using
the GID group to report breakbulk movements and the EQD Group to report movements of equipment.
This guideline provides for the transmission of multiple equipment movements, through repetition of the
EQD Group. The design of the CODECO message allows for the reporting of transport details associated
with a container at both message level or EQD level.
Where appropriate, main carriage (ie. Ocean transport) details may be specified in the TDT Group at
message level. Inland transport details (ie. road, rail or barge) associated with a movement into and out of a
facility must always be reported at the EQD level.
The current design of the CODECO message allows for only one repetition of the TDT Group at message
level. As a result, only one main carriage (ocean vessel) can be specified for all containers reported in each
message at EQD level. Where the message is used to report multiple equipment movements, a facility
would therefore be obliged to sort movements according to main carriage before transmission, and send one
CODECO per vessel.
This approach does not align with business practice in many regions, including North America and
Australia/New Zealand, where gate movements are currently reported on a random one-message-per
movement basis without any sorting by main carriage.
It should be noted that the usage of the CODECO outlined in this guideline will be applied in some regions
on a one-message-per-movement basis (ie. only one repetition of the EQD Group) to facilitate
implementation without substantial re-design of established systems. Although the Guideline provides for
up to 999 repetitions of the EQD Group, only one will be used.
Other regions may choose to adopt a multiple-movement-per-message usage (ie. multiple EQDs), if this
aligns with local business practice.
Global users should be aware that these different approaches will be implemented in different regions, and
should make allowances accordingly.
Discussions will be held within ITIGG and the JM4 Transport Group towards preparing changes to future
versions of the CODECO message which will allow multiple repeats of the TDT Group at message level,
and a means of associating each repetition of the EQD Group with a particular main carriage TDT.
Until such time as this process has been completed and the EDIFACT message is enhanced, users are
advised to implement according to the principle outlined above.
This does not apply in situations where main carriage is not to be reported. In these cases, multiple
repetitions of the EQD Group may be transmitted, provided this aligns with business practice. Global users
should, however, be aware that communities in regions where one-message-per-movement already prevails
are likely to implement according to this principle even where Main Carriage is not required.
BREAKBULK CARGO
Where the message is to be used to report breakbulk cargo movements, breakbulk cargo items should be
identified using the GID Group. If no equipment is associated with the movements being reported, at least
one repeat of the EQD in Group 5 is required (because the group is mandatory) with the code “BB”
(breakbulk) in DE 8053.
This reflects the fact that this message has been primarily designed to report the movement of containers.
In this Guideline the FTX at EQD level has been used for transmission of a variety of coded information,
including codes which report on the status of the item of equipment.
This usage has been agreed as a temporary measure until such time as clear industry requirements emerge
from live usage of the message, and a number of changes to the CODECO message are completed in future
versions. It is likely that new segments will be inserted in future versions of CODECO, or new codes
specified in future versions of the EDIFACT code list, to cover functions performed by the EQD level FTX
in this guideline. This is not, however, likely to occur for some years.
The GID Group is designed to provide cargo information, which is in fact a secondary consideration in
messages reporting equipment movements. In this guideline it has been made available to provide brief
cargo detail where it is required by users.
The GID Group in the CODECO message is not intended to be used as a primary source of information for
generation of commercial records such as a ship’s manifest. This function is better performed using
consignment-based messages (such as the IFTM Set) which are intended for this purpose.
The majority of users will only use the GID Group in the CODECO message for reporting supplementary
information, such as temperature or dangerous goods details relating to cargo in a full container or a pre-set
setting on an empty container. It is already apparent that these users will therefore not require the GID
segment other than as a dummy value to trigger the GID Group. This usage has been provided for in the
guideline.
All users should be aware that in the longer term some key segments (such as TMP/RNG and DGS/FTX)
may be added to the EQD Group to allow those users who do not require the full GID Group to dispense
with the group altogether.
The DAM/COD Group can be used at EQD level to detail any damage to an item of equipment, if a detailed
inspection has been carried out at the time of the movement being reported. In most cases, however, such a
detailed inspection will not be carried out until after a movement has taken place.
In some regions a general indication of damage condition will be transmitted in the FTX under EQD in this
message (if damage has been identified at the time of the movement), and that detailed damage information
follow later using the DESTIM message, which is designed for this purpose. This approach is likely to be
adopted in North America and Australia/New Zealand.
In other regions the DAM/COD Group in the CODECO message may be used for detailed reports. As with
the note above regarding the use of the EQD Group, global users should be aware that different approaches
will be adopted in different regions.
SEGMENT TABLE
HEADER SECTION
Segment Function: To head and identify the message type and version.
R CODECO
R 95B
R UN
Segment Function: To indicate the type and function of a message and to transmit the identifying
number.
NOTE:
The codes [44] and [46] have been included in this guide to cover reports of equipment movements to and
from rail (ie. land-side). The COARRI message is designed for reporting movements onto and off a vessel
(ie. ship side).
Clarification: The FTX segment at this level may be sent to provide free text comments or
supplementary information, or a coded indication what data is being changed if
the message is an amendment to a previous transmission.
O RFF REFERENCE
Clarification: The RFF at this level is used to transmit references which apply to the whole
message, and which link the message to earlier messages, orders or authorisations
which relate to the equipment movement.
R Reference Number
Group Function: A group of segments to indicate information regarding the main carriage.
Group Repeats: 1
Group Status: Conditional
Group Usage: Optional
Clarification: The TDT Group at this level identifies the main (ocean) carriage details for all
items of equipment in the message, where this is applicable. Where main
carriage details are not relevant or not known at the time of the reported
movement, the segment is not required at this level.
Segment Function: To specify the transport details such as mode of transport, means of transport, its
conveyance reference number and the identification of the means of transport.
O C040 CARRIER C
O 3127 Carrier identification C an..17
R Carrier code
D 20 BIC
D 87 Assigned by Carrier
D 166 UN NMFCA (SCAC)
D 184 ACOS
D 11 Lloyd’s Register
D ZZZ Mutually Agreed
O RFF REFERENCE
Clarification: The RFF at this level is used to transmit voyage numbers where an alternative
number is used in addition to that quoted in the preceding TDT.
Clarification: The LOC at this level identifies locations associated with the main carriage.
D 7 Place of Delivery
D 8 Place of Destination
D 9 Place/port of Loading (Operational Port of Loading)
D 11 Place/port of discharge (Operational Port of Discharge)
D 33 Baseport of discharge
D 34 Baseport of loading
D 88 Place of Receipt
D UN LOCODE
D EAN Location Code
D US Census Code
R 139 Port
D [BER] Berths
D [WHA] Wharves
D [TER] Terminals
D [GAT] Gates
D [WAR] Warehouses
D [CNE] Consignee’s Premises
D [CNR] Consignor’s Premises
D [PAC] Packing/unpacking facilities
D [STO] Storage facilities
D [REP] Repair facilities
D 9 EAN
D 184 ACOS
D ZZZ Mutually Agreed
D [BER] Berths
D [WHA] Wharves
D [TER] Terminals
D [GAT] Gates
D [WAR] Warehouses
D [CNE] Consignee’s Premises
D [CNR] Consignor’s Premises
D [PAC] Packing/unpacking facilities
D [STO] Storage facilities
D [REP] Repair facilities
D 9 EAN
D 184 ACOS
D ZZZ Mutually Agreed
Clarification: The DTM at this level is used to report dates and times relating to the
vessel/voyage in the TDT.
M C507 DATE/TIME/PERIOD M
M 2005 Date/time/period qualifier M an..3
R Date/time
D 203 CCYYMMDDHHMM
Group Function: A group of segments to identify a party and/or addresses and related contacts.
Group Repeats: 9
Group Status: Mandatory
Group Usage: Mandatory
Clarification: This segment group is mandatory in the message and must always be used.
Segment Function: To specify the name/address and their related function, either by CO82 only
and/or unstructured by CO58 or structured by CO80 thru 3207.
Clarification: The NAD segment at this level must always be sent. It identifies parties
associated with all the equipment movements reported in the message.
R Company code
D 7 CEFIC
D 9 EAN
D 10 ODETTE
D 16 DUNS
D 20 BIC
D 87 Assigned by carrier
D 163 UN FMC (US freight forwarders)
D 166 US NMFCA (SCAC)
D 184 Australian Chamber of Shipping
R Party Name
D C059 STREET C
M 3042 Street and number/p.o. box M an..35
O 3042 Street and number/p.o. box C an..35
O 3042 Street and number/p.o. box C an..35
R Street Address
R City
R State/province
R Post Code
Clarification: The CTA identifies a specific contact party for the entity specified in the
preceding NAD.
R IC Information Contact
R Name
Clarification: The GID Group may be used to provide goods or cargo detail related to an item
of equipment where this is required by the receiving party.
Clarification: The GID segment must always be sent if Group 3 is used. Some users may wish
to use a dummy value in DE 1496 in order to access other segments in the GID
Group (such as the TMP or TGS) which do not appear at the EQD level.
R Number of packages
Clarification: The HAN allows for coded or free text handling instructions relating to the goods
item.
D 9 EAN
D 184 ACOS
Clarification: The FTX at this level provides a free text goods description.
Clarification: The FTX at this level may be used for a commodity code.
D 1 Additional identification
D 5 Product Identification
R Item Number
O MEA MEASUREMENTS
Segment Function: To specify physical measurements, including dimension tolerances, weights and
counts.
Clarification: The MEA at this level reports measurements related to the goods item.
R AAE Measurement
D ABJ Volume
D G Gross Weight
D T Tare Weight
D WT Weight
R C174 VALUE/RANGE C
M 6411 Measure unit qualifier M an..3
D LBR Pounds
D KGM Kilogram
D FTQ Cubic Feet
D MTQ Cubic metres
D TMP TEMPERATURE
Clarification: The TMP should always be sent where temperature-sensitive cargo is carried in
an item of equipment. If a temperature range is to be specified, the TMP should
be used in conjunction with the RNG segment - in this case only DE 6245 of the
TMP should be used, and the temperature range should be specified in the RNG.
If a single temperature setting is to be specified, C239 in the TMP should be
used.
R 2 Transport Temperature
R Temperature setting
D CEL Celsius
D FAH Fahrenheit
Clarification: The RNG segment may be used to specify a range of temperatures, if applicable.
It should always be used in conjunction with the preceding TMP segment.
R 5 Temperature Range
R C280 RANGE C
M 6411 Measure unit qualifier M an..3
D CEL Celsius
D FAH Fahrenheit
R Minimum temperature
R Maximum temperature
Clarification: The SGP segment is used to link a goods item to a particular item of equipment
detailed in the EQD group.
Group Function: A group of segments to specify dangerous goods details related to a goods item.
Group Repeats: 9
Group Status: Conditional.
Group Usage: Dependent
Clarification: This group of segments should always be sent if dangerous goods are carried in
an item of equipment.
R UNDG Number
R Flashpoint
D CEL Celsius
D FAH Fahrenheit
D 1 Great Danger (= I)
D 2 Medium Danger (= II)
D 3 Minor Danger (= III)
R EMS Number
R MFAG Number
R DG Label Marking 1
R DG Label Marking 2
R DG Label Marking 3
Clarification: The FTX at this level should always be sent at least once to specify the technical
name of the dangerous goods described in the preceding DGS segment
D P Marine Pollutant
D PP Severe Marine Pollutant
Group Function: A group of segments to specify containers in which goods are transported.
D [BB] Breakbulk
D CH Chassis
D CN Container
D RG Reefer Generator
D SW Swap Body
D TE Trailer
R Size/type code
D 1 Shipper Supplied
D 2 Carrier Supplied
D 3 Third Party Supplied
D 1 Continental
D 2 Export
D 3 Import
D 6 Transhipment
D 4 Empty
D 5 Full
D 6 No volume available (unknown)
R RFF REFERENCES
Segment Function: A segment to specify the identifying number associated with the container, such
as:
- container sequence number
- booking reference number (sea)
Clarification: The RFF at this level is used to specify reference numbers related to the item of
equipment.
R C506 REFERENCE M
R 1153 Reference qualifier M an..3
R Reference number
NOTE:
Code values marked with * are not currently in Recommendation JM4/261, but have been proposed for
inclusion.
Segment Function: To specify transport movement details for a goods item or equipment.
Clarification: The TMD may be used to report transport movement details for the item of
equipment in the EQD.
D 2 LCL/LCL (= PP = CFS/CFS)
D 3 FCL/FCL (= HH = CY/CY)
D 4 FCL/LCL (= HP = CY/CFS)
D 5 LCL/FCL (= PH = CFS/CY)
Clarification: The DTM at this level is used to report dates and times relating to the item of
equipment.
M C507 DATE/TIME/PERIOD M
M 2005 Date/time/period qualifier M an..3
D 7 Effective Date/time
D 36 Expiry date (date license expires)
D 94 Manufacture Date
D 181 Positioning date
D 201 Pickup date/time of equipment (actual)
D 371 Hydrotest Date
D 376 Bi-annual Terminal Inspection Date
D 377 Federal Highway Administration (FHWA) Inspection date
D 378 Container Safety Convention (CSC) Inspection date
D 379 Periodic Inspection Date
R Date/time
D 102 CCYYMMDD
D 203 CCYYMMDDHHMM
D 303 CCYYMMDDHHMMZZZ
D 718 CCYYMMDD-CCYYMMDD (dash is not transmitted)
R LOC LOCATION
Segment Function: A segment to specify ports/locations associated with the transport of a container,
such as:
- stowage cell
- place of discharge
Clarification: The LOC segment at this level is used to report locations which relate to the
movement of the item of equipment.
D 8 Place of Destination
D 9 Operational Port of loading
D 11 Operational Port of discharge
D 76 Original Port of loading
D 147 Stowage Cell
D 164 Final Port of Destination
D [165] Activity Location
D UN LOCODE
D Stowage cell
D EAN Location Code
R 139 Port
D [BER] Berths
D [WHA] Wharves
D [TER] Terminals
D [GAT] Gates
D [WAR] Warehouses
D [CNE] Consignee’s Premises
D [CNR] Consignor’s Premises
D [PAC] Packing/unpacking facilities
D [STO] Storage facilities
D [REP] Repair facilities
D 9 EAN
D 184 ACOS
D ZZZ Mutually Agreed
D [BER] Berths
D [WHA] Wharves
D [TER] Terminals
D [GAT] Gates
D [WAR] Warehouses
D [CNE] Consignee’s Premises
D [CNR] Consignor’s Premises
D [PAC] Packing/unpacking facilities
D [STO] Storage facilities
D [REP] Repair facilities
D 9 EAN
D 184 ACOS
D ZZZ Mutually Agreed
O MEA MEASUREMENTS
Segment Function: To specify physical measurements, including dimension tolerances, weights and
counts.
Clarification: The MEA segment at this level is used to report weights which relate to the
equipment.
R AAE Measurement
R C174 VALUE/RANGE C
R 6411 Measure unit qualifier M an..3
D CMT Centimetres
D INH Inches
D KGM Kilogram
D MTQ Cubic metres
D LBR Pounds
O DIM DIMENSIONS
Clarification: The DIM segment at this level is used where dimensions exceed those of the
standard reported in the preceding EQD. It relates to out-of-gauge cargo with the
equipment in or on which it is carried.
D 1 Gross Dimensions
D 5 Off-standard dimension front
D 6 Off-standard dimension back
D 7 Off-standard dimension right
D 8 Off-standard dimension left
D 9 Off-standard dimension general
D 10 External equipment dimension
M C211 DIMENSIONS M
M 6411 Measure unit qualifier M an..3
D CMT Centimetres
D INH Inches
R Length
R Width
R Height
D TMP TEMPERATURE
Message Level: Group 3 (Not in D95B. DMRs will be lodged to add the TMP at this level)
Segment Repeats: 9
Segment Status: Conditional.
Segment Usage: Dependent
Sample Segment: TMP+2+1.0:CEL’
Clarification: The TMP should always be sent where temperature-sensitive cargo is carried in
an item of equipment. If a temperature range is to be specified, the TMP should
be used in conjunction with the RNG segment - in this case only DE 6245 of the
TMP should be used, and the temperature range should be specified in the RNG.
If a single temperature setting is to be specified, C239 in the TMP should be
used.
R 2 Transport Temperature
R Temperature setting
D CEL Celsius
D FAH Fahrenheit
Message Level: Group 3 (Not in D95B. DMrs will be lodged to add the RNG at this level)
Segment Repeats: 9
Segment Status: Conditional.
Segment Usage: Optional.
Sample Segment: RNG+5+CEL:0.5:1.5’
Clarification: The RNG segment may be used to specify a range of temperatures, if applicable.
It should always be used in conjunction with the preceding TMP segment.
R 5 Temperature Range
R C280 RANGE C
M 6411 Measure unit qualifier M an..3
D CEL Celsius
D FAH Fahrenheit
R Minimum temperature
R Maximum temperature
Clarification: The SEL segment should be used whenever seal information is required by the
receiving party.
R Seal number
D [QA] Quarantine
D CA Carrier
D CU Customs
D SH Shipper
D TO Terminal Operator
D AA Consolidator
D AB Unknown
D 1 In right condition
D 2 Damaged
Clarification: The FTX segment at this level is used to provide a variety of coded or free text
information related to the item of equipment.
D 5 ISO
D 184 ACOS
Clarification: The EQA may be used to identify any secondary equipment attached to the item
specified in the preceding EQD segment.
D AB Chain
D AD Temperature probe
D BL Blocks
D BR Barge
D CH Chassis
D CN Container
D FSU Forked Support
D LAR Lashing Rope
D RG Reefer Generator
D RR Rail Wagon
D STR Strap
D TE Trailer
D TP Tarpaulin
R Equipment number
Group Function: A group of segments to specify damage details related to the equipment.
Group Repeats: 9
Group Status: Conditional
Group Usage: Optional
Clarification: The DAM/COD Group can be used at this level to detail any damage to an item
of equipment, if a detailed inspection has been carried out at the time of the
movement being reported. In most cases, however, such a detailed inspection
will not be carried out until after a movement has taken place.
M DAM DAMAGE
Segment Function: A segment to specify equipment damages, such as the point of the damage on the
equipment, and the type of damage.
R 1 Equipment damage
O C826 ACTION C
R 1229 Action request/notification, coded C an..3
Group Function: A group of segments to indicate details of the movement of containers by sea
and by inland carriers, such as mode and means of transport and locations.
Group Repeats: 9
Group Status: Conditional
Group Usage: Optional
Clarification: The TDT Group at this level is used to specify details of inland transport related
to the equipment.
Segment Function: To specify the transport details such as mode of transport, means of transport, its
conveyance reference number and the identification of the means of transport.
The segment may be pointed to by the TPL segment.
R 1 Inland Carriage
R Carrier’s number
D 1 Maritime
D 2 Rail
D 3 Road
D 4 Air
D 8 Inland Water
O C040 CARRIER C
O 3127 Carrier identification C an..17
R Carrier Code
D 20 BIC
D 87 Assigned by Carrier
D 166 US, National Motor Freight Classification Assoc (SCAC)
D 184 ACOS
D 11 Lloyd’s Register
D ZZZ Mutually Agreed
R LOC LOCATION
Segment Function: A segment to specify ports/locations associated with the transport of a container.
Clarification: The LOC segment at this level is used to report a location related to the inland
transport movement.
D UN LOCODE
D EAN Location Code
D US Census Code
R 139 Port
D 6 UN/ECE
D 9 EAN
D 112 US Census
D [BER] Berths
D [WHA] Wharves
D [TER] Terminals
D [GAT] Gates
D [WAR] Warehouses
D [CNE] Consignee’s Premises
D [CNR] Consignor’s Premises
D [PAC] Packing/unpacking facilities
D [STO] Storage facilities
D [REP] Repair facilities
D 9 EAN
D 184 ACOS
D ZZZ Mutually Agreed
D [BER] Berths
D [WHA] Wharves
D [TER] Terminals
D [GAT] Gates
D [WAR] Warehouses
D [CNE] Consignee’s Premises
D [CNR] Consignor’s Premises
D [PAC] Packing/unpacking facilities
D [STO] Storage facilities
D [REP] Repair facilities
D 9 EAN
D 184 ACOS
D ZZZ Mutually Agreed
Clarification: The DTM at this level is used to report dates and times relating to the movement
in the preceding TDT.
M C507 DATE/TIME/PERIOD M
R Date/time
D 203 CCYYMMDDHHMM
D 303 CCYYMMDDHHMMZZZ
Segment Function: To specify the name/address and their related function, either by CO82 only
and/or unstructured by CO58 or structured by CO80 thru 3207.
Clarification: The NAD segment at this level can be used to identify parties associated with the
item of equipment.
R Company code
D 7 CEFIC
D 9 EAN
D 10 ODETTE
D 16 DUNS
D 20 BIC
D 87 Assigned by carrier
D 163 US FMC (US Freight Forwarders)
D 166 US NMFCA (SCAC)
D 184 ACOS
D C059 STREET C
O 3042 Street and number/p.o. box M an..35
O 3042 Street and number/p.o. box C an..35
O 3042 Street and number/p.o. box C an..35
R Street Address
R City
R State/Province Code
R Post Code
SUMMARY SECTION
Clarification: The CNT segment is Mandatory in the message and must always be sent,
regardless of whether a control total is required by the receiving application. If
no total is required, the segment may be used with dummy values in order to
comply with EDIFACT requirements.
M C270 CONTROL M
M 6069 Control qualifier M an..3
D 1 Dummy Value
D 16 Total Number of Equipment
R Number of segments
*****
Ref: itigg\105.v14