Wednesday, 22 September 2010

COREOR, PIN number

For security issues, you might wish to add a PIN number to your COREOR message.

PIN number can be stored in RFF segment; in the above sample, I used qualifier RE (Release Number) as c506.1153 in order to assign to my container a PIN number:

(...)
EQD+CN+GEKU1234567+22G1:102:5++3+5'

RFF+CN:SAL/01'
 
RFF+RE:QY879' 
RFF+SQ:0001'
MEA+AAE+G+KGM:23817'
(...)

Monday, 20 September 2010

UN/LOCODE

UN/LOCODE is a geographic coding scheme developed and maintained by UNECE a unit of the United Nations

It assigns aproximatly 40.000 code elements to locations names of ports, airports, rail and road terminals, postal exchange offices, border crossing points and other locations used in trade and transport in 234 countries.

UN/LOCODE
typically have 5 characters. The first 2 are letters, and come from the ISO 3166-1 country codes. Normally 3 letters will follow, but if there are not enough combinations, also numbers can be used.

Some samples: 
  • DEBER for Berlin in Germany (DE) 
  • NLAMS for Amsterdam in NL 
  • USNYC for New York City in US
In order to browse through LOCODEs you can use the useful web services developed by UNECE or Antwerp Port Authority.

I would like to thanks www.knowledgerush.com as source for this post.


COREOR, general infos

Purpose of the message: COREOR is used to release full import/export containers.

Parties involved: the message is normally sent by Carrier/Liner Agent to Terminal Operator.

I have seen several Carriers to use the COREOR to release empty transport equipment prior to packing but, based on ITIGG recommendations, COPARN should be used.

Here below a very basic sample of COREOR message:

UNB+UNOA:1+SENDER-ID+RECEIVER-ID+100920:1000+1'
UNH+2+COREOR:D:95B:UN'
BGM+12+3+9'
RFF+BM:SAL/01'
TDT+20+00018N+1++GEK:172:20+++47AVS:103::SALERNO PRIDE'
RFF+VON:0123N'
NAD+CA+GEK:172:20'
EQD+CN+GEKU1234567+22R1:102:5++3+5'
RFF+SQ:1'
CNT+16:1'
UNT+10+2'
UNZ+1+1'

Tuesday, 13 July 2010

COHAOR, inspection confirmation

In the previous sample a Local Forwarder was requesting to Terminal Operator to handle an inspection.

Here below here is Terminal Operator confirmation: container will be put aside, at a certain date/time, in order to be inspected.

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+100713:1200+1'
UNH+2+COHAOR:D:95B:UN:ITG13'
BGM+702+2+9'
DTM+137:201007131200:203'
FTX+AAI+++INSPECTION CONFIRMATION'
NAD+MS+SCT:160'
NAD+CF+GEK:172:87'
EQD+CN+GEKU1234567+4210:102:5++3+5'
RFF+CN:SAL/01'
DTM+7:201007140900:203'
LOC+165+ITSAL:139:6+SCT:TER:ZZZ'
FTX+AAA++GENERAL CARGO'
HAN+SP:130:184:EQUIPMENT PUT ASIDE FOR INSPECTION'
TDT+20+00018N+1+13+GEK:172:87+++47AVS:103::SALERNO PRIDE'
NAD+SLS+GEK:172:87'
CNT+1:1'
UNT+16+2'
UNZ+1+1'

COHAOR, general infos and inspection request

Purpose of the message: COHAOR is an order to perform specified special handlings and/or services on items of transport equipment.

Parties involved: message can be sent by Liner Agent / Local Forwarders to Terminal and vice versa.

I have drafted a sample based on:
  • ITIGG Guideline 
  • JM4/ITIGG/120/v.16.
 In this sample a Local Forwarder is requesting to the Terminal to handle a Custom Inspection on a certain date.

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+100713:1000+1'
UNH+2+COHAOR:D:95B:UN:ITG13'
BGM+702+2+9'
DTM+137:201007131000:203'
FTX+AAI+++INSPECTION REQUEST'
NAD+MS+LOCAL AGENT:160:87'
NAD+CF+GEK:172:87'
EQD+CN+GEKU1234567+4210:102:5++3+5'
RFF+CN:SAL/01'
DTM+7:20100714:102'
LOC+165+ITSAL:139:6+SCT:TER:ZZZ'
FTX+AAA++GENERAL CARGO'
HAN+63:130:184:TO BE INSPECTED'
TDT+20+00018N+1+13+GEK:172:87+++47AVS:103::SALERNO PRIDE'
NAD+SLS+GEK:172:87'
CNT+1:1'
UNT+16+2'
UNZ+1+1'

Tuesday, 15 June 2010

COARRI, over-height container to be transhippend onto feeder

That's a sample about an over-height container to be transhipped onto a feeder vessel.

(...)
EQD+CN+GSLM1506100+22U1:102:5++6+5'
RFF+BN:SAL/01'
DTM+203:201006151030:203'
LOC+9+SGSIN:139:6'
LOC+147+0330406::5’
MEA+WT+G+KGM:11490'
DIM+9+CMT:::55'
SEL+6789+CA'
FTX+AAA+++MACHINE PARTS'
TDT+30+00019N+1+11+GEK:172:87+++47AVS:103'
LOC+7+ITGIT:139:6'
DTM+133:201006161400:203'
(...)

Monday, 10 May 2010

COARRI, brief indication about container repair condition

In some circumstances it may be useful to state, into COARRI, a brief indication about the container repair condition. Let's see a sample:

(...)
MEA+AAE+T+KGM:3800'

MEA+AAE+G+KGM:23870'
SEL+0068856+CA+1'
FTX+DAR++5:ZZZ:184+AWAITING INSPECTION'
CNT+16:1'
(...)

A detailed documentation about the usage of the Indication of Damage Condition (DAR) is provided by ITIGG (International Transport Implementation Guidelines Group) here under the section "Code List for the FTX Segment".