Showing posts with label COARRI. Show all posts
Showing posts with label COARRI. Show all posts

Friday, 4 April 2014

COARRI based on Vessel Carrier Operator

Recently I have received a couple of requests concerning the chance to receive COARRI based on Vessel Carrier Operator.

The basic idea is the following:
  1. Vessel Carrier Operator receives BAPLIE and/or COARRI for all the lines on board; 
  2. Lines, which obtain allocation on a third party vessel, receive COARRI for their containers. 
That's a sample of COARRI used to accomplish item #1: 

UNH+1396271822440+COARRI:D:95B:UN:ITG12'
BGM+98:::DISCHARGING REPORT+10331485800001+9'
TDT+20+XXX1314D+1+13+CARRIER-ID:172:20+++XXXX:103::VESSEL NAME'
LOC+11+ITSAL:139:6+SCT:TER:ZZZ'
DTM+132:201403310800:203'
DTM+133:201403311400:203'
NAD+CA+CARRIER-ID:160:20'
EQD+CN+ABCD1220790+22G1:102:5++6+5'
RFF+BN:S3-08764104'
DTM+203:201403310913:203'
LOC+9+ITPMO:139:6'
MEA+AAE+G+KGM:27320'
MEA+AAE+T+KGM:1900'
SEL+PA004641'
FTX+AAA+++PASTA ALIMENTARE'
FTX+DAR++6:ZZZ:184+NOT DAMAGED'
TDT+30+XXX150A+1+13+CARRIER-ID:172:20+++XXXX:103'
LOC+7+GBPRU:139:6'
NAD+CF+LINE-ID:160:20'
EQD+CN+ABCD1186248+22G1:102:5++6+5'
RFF+BN:S3-08764135'
DTM+203:201403310912:203'
LOC+9+ITPMO:139:6'
MEA+AAE+G+KGM:27320'
MEA+AAE+T+KGM:1900'
SEL+PA004675'
FTX+AAA+++VINO'
FTX+DAR++6:ZZZ:184+NOT DAMAGED'
TDT+30+XXX150A+1+13+CARRIER-ID:172:20+++XXXX:103'
LOC+7+GBPRU:139:6'
NAD+CF+LINE-ID:160:20'
CNT+16:20'
UNT+213+1396271822440'

The code used at NAD.NAD level in NAD02 is the Vessel Carrier Operator ID

The code used at EQD.NAD level in NAD02 is the Line ID.

Sunday, 18 November 2012

COARRI report vs time based COARRI

Basically there are two ways to send COARRI to an EDI customer: 
  1. Based a time interval (eg. every 5-minutes); 
  2. When all containers have been discharged/loaded from/to vessel. 
The first type of COARRI implies that an unpredictable number of interchanges have been sending to the EDI customer based a time interval. 

The second type of COARRI implies that up to two interchanges (eg. 1 COARRI discharge and 1 COARRI loading) have been sending to the EDI customer. 

Both the ways are valid but I manly use the first one for the following reasons: 
  1. To be updated, in (almost) real time, about vessel status is indeed big advantage; 
  2. In case containers discharged from vessel are going to be released before the end of vessel operations the EDI customer will still receive first the COARRI and then the CODECO; 
  3. Often, receiving COARRI in duly time allows EDI customer to cater the corresponding EDI (eg. COREOR) and speed-up Terminal operations without accumulating too many EDI to be processed at the very last minute.

Wednesday, 1 February 2012

Gross weight in EDI transmissions

Recently an EDI customer reported me an issue related to the weights stated into BAPLIE / COARRI of my production environment. 

I was a little bit surprised in discover a coarse translation error in MEA segment concerning c502.6313 (ie. measurement dimension): I used the qualifier G (ie. weight of goods including packing but excluding the carrier's equipment) in order to report the weight of the goods plus carrier's equipment. 

Checking on the ITIGG guidelines I found out the new qualifier EGW which is used in order to declare the gross weight including carrier's equipment.

Here below how the change affected my EDI transmissions: 
 
Carrier's COPRAR Loading:

(...)
EQD+CN+ABCD1234567+45R1:102:5++2+5'
RFF+BN:ORDER-1' 
TMD+3' 
LOC+9+ITSAL:139:6+:BER:ZZZ:SALERNO CONTAINER TERMINAL'
LOC+11+CAMTR:139:6' 
LOC+7+CATOR:139:6' 
MEA+AAE+T+KGM:4550' 
MEA+AAE+G+KGM:22730' 
TMP+2+012:CEL' 
(...)


Terminal's COARRI Loading: 
(...) 
EQD+CN+ABCD1234567+45R1:102:5++2+5'
RFF+BN:ORDER-1'
TMD+3'
DTM+203:201201221233:203'
LOC+11+CAMTR:139:6'
LOC+7+CATOR::6'
LOC+147+340708::6'
MEA+AAE+T+KGM:4550'
MEA+AAE+EGW+KGM:27280'
TMP+2+12.0:CEL'
(...)
 
Terminal's BAPLIE departure: 
(...)
LOC+147+0340708::5' 
MEA+WT++KGM:27280'
TMP+2+012:CEL'
LOC+6+ITSAL'
LOC+12+CAMTR'
LOC+83+CATOR'
RFF+BM:1'
EQD+CN+ABCD 1234567+45R1+++5'
NAD+CA+XXX:172:20'
(...)
 

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".


Wednesday, 14 April 2010

COARRI, general infos

Purpose of the message: the COARRI message is used to confirm that containers have been discharged/loaded from/on a sea going vessel. COARRI is also used to confirm that containers have been shifted or restowed on board a vessel.
Parties involved: message is normally sent by Terminal Operator to Line or Liner Agent.

Here below a sample of COARRI, loading:

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+100414:1014+1269953057176'
UNH+1269953057162+COARRI:D:95B:UN:ITG12'
BGM+270:::LOADING REPORT+06806003300003+9'
FTX+OSI++L'
TDT+20+00018N+1+13+GEK:172:87+++47AVS:103::SALERNO PRIDE'
LOC+9+ITSAL:139:6'
DTM+132:201004140600:203'
DTM+133:201004141400:203'
NAD+CA+GEK:172:ZZZ'
EQD+CN+GEKU1234567+4210:102:5++2+5'
RFF+BN:SAL/01'
DTM+203:201004141010:203'
LOC+11+ILHFA:139:6'
LOC+7+ILHFA:139:6'
LOC+147+200414::5'
MEA+AAE+T+KGM:3500'
MEA+AAE+G+KGM:23000'
SEL+5178170+TO+1'
FTX+DAR++6:ZZZ:184+NOT DAMAGED'
CNT+16:1'
UNT+21+1269953057162'
UNZ+1+1269953057176'