The impact of SOLAS on COPARN

VGM can be sent from Line to the Terminal operator, via COPARN, before container arrives full via truck.

Here below a sample:

UNH+00000000006944+COPARN:D:95B:UN:SMDG16'
BGM+11+800255846++AB'
RFF+BN:800255846'
TDT+20+048R+1++TEST:172:20+++CALL_SIGN:103::TEST_VESSEL:PA'
RFF+VON+048'
LOC+9+AUMEL:139:6:MELBOURNE+CONWS: TER:ZZZ:P&O PORTS'
DTM+132:200212290600:203'
NAD+MS+LINE:172:20'
CTA+IC+:STAN MATTHEWS'
EQD+CN++4532:102:5+2+2+5'
RFF+SQ:1'
EQN+1'
TMD+3++1'
DTM+798:200211211700:203'
LOC+11+ZACPT:139:6'
LOC+8+ZAJNB:139:6'
MEA+AAE+VGM+KGM:10474'
TMP+2+011:CEL'
FTX+AAA+++CHOCOLATES'
FTX+ABS++SM1:ZZZ:SMD’
TDT+1++3'
DTM+132:200212270600:203'
LOC+165+AUMEL:139:6'
NAD+AM+++JOHN DILLINGER’
CNT+16:1'
UNT+26+00000000006944'

Note the below codes:

    1) EQD.DTM; DTM01=798 (Data/Time weight verification)
    2) EQD.MEA: MEA02=VGM (Verified Gross Weight);
    3) EQD.FTX: SM1 (SOLAS verification method used);
    4) In NAD: NAD01=AM (EDI SIGNATURE).

The above sample (vers. D95B) comes from SMDG MIG: I have uploaded it here for your guide.

Main carriage transport in COPARN

An error that often I have to handle manually in my EDI environment concerns the 'Main Carriage Transport' declared in the H.TDT.TDT segment of some COPARN messages.

Let’s have a look at the following sample:

(...)
TDT+20+2036+1++XXX:172:166+++XXX:103::VESSEL NAME'
LOC+9+ITGOA:139:6:GENOA'
LOC+11+AUMEL:139:6:MELBOURNE'
DTM+133:201209030000:203'
NAD+CF+XXX:172:166'
NAD+MR+ITSALSCT’
EQD+CN++22GP:102:5++2+4'
RFF+SQ:001'
EQN+1'
LOC+163+AUMEL:139:6:MELBOURNE'
MEA+AAE+X+KGM:19250'
TDT+1+TRANSPORTER+3'
LOC+165+ITSAL:139:6:SALERNO'
(...)

That’s a COPARN concerning a container with the following characteristics:

1. To be loaded onto a vessel qualified as 'Main Carriage Transport';
2. Loading port: Genoa (ITGOA);
3. Place/Port of discharge: Melbourne (AUMEL);
4. Place/Port of destination for stowage purposes: Melbourne (AUMEL);
5. Activity Location: Salerno (ITSAL).

So here is the final container route:

1. Collected/Deivered at Salerno port;  
2. Loaded from Salerno to Genoa Port by a feeder vessel;  
3. Transhipped from Genoa to Melbourne Port by the mother vessel declared in the TDT segment.

Of course not always mother vessels, operational on external quays,  are stored into my system and unfortunately affected COPARN messages get rejected due to missing valid vessel call.

COPARN, showing shipper infos

In some circumstances, Carrier/Liner Agent can use the empty release COPARN to arrange transport with Trucking Company.

Since now COPARN is also sent to Trucking Company, it's very useful to add some extra infos about the place where to collect the goods.

Let's use the NAD segment, at NAD segment group level, in order to state:

• Sender Shipper code (C082.3039);
• Sender Shipper description (C058.3124) ;
• Shipper address (C058.3124) ;
• Shipper telephone number (C058.3124) .

...
NAD+MS+GEKSEPPE:172:ZZZ'
NAD+CA+GEK:172:20'
NAD+CZ+01+MOZZARELLA BELLA:VIA SOLE 12, SALERNO:84100 SALERNO, IT:TEL ?+39089123456'
EQD+CN++4510:102:5++2+4'
...

COPARN, showing the second on-carriage transport

That's a sample to state into a Full-In COPARN the second on-carriage transport:

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090730:1323+1'
UNH+2+COPARN:D:00B:UN:SMDG20'
BGM+126+3+9'
DTM+137:200907301523:203'
RFF+BN:SAL/01'
DTM+36:200908101200:203'
TDT+20+00018N+1++GEK:172:87+++47AVS:103::SALERNO PRIDE'
RFF+VON:GKS01A'
LOC+9+ITSAL:139:6'
DTM+132:200908091200:203'
NAD+FW+0001+FORWARDING PARTY'
NAD+CA+GEK:172:ZZZ'
NAD+MS+GEK:172:ZZZ'
CTA+IC+:GEKSEPPE'
COM+0039089230550:TE'
EQD+CN+GEKS1504090+45G1:102:5+2+2+5'
RFF+BN:SAL/01'
EQN+1'
TMD+3++2'
LOC+8+GWOXB:139:6'
LOC+98+ITSAL:139:6'
LOC+11+ESALG:139:6'
MEA+AAE+AET+KGM:10474'
MEA+AAE+T+KGM:4200'
SEL+00214784+SH+1'
FTX+AAA+++VARIOUS, NOS'
TDT+30+09+1++XXX:172:87+++478AWD:103::WET OCEAN'
DTM+132:200908130600:203'
LOC+11+GWOXB:139:6'
CNT+16:1'
UNT+30+2'
UNZ+1+1'

COPARN

Formal Definition: The message contains an order to release, to make available, to accept, to call down containers or to announce the impending arrival of containers.

Some samples of message usage:

• Requesting or authorising acceptance of an empty container;
• Requesting or authorising acceptance of a full container;
• Releasing an empty container for packing;
  
• Requesting or authorising an on/off hire transaction.

In any case, COPARN message will be 'answered' by a CODECO message confirming that the equipment movement or status change has been taken place.

Here below a very basic COPARN sample used to release an empty container expected to be loaded on vessel:

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090722:0800+1'
UNH+2+COPARN:D:95B:UN:ITG11'
BGM+12:::RELEASE ORDER+3+9'
RFF+BN:SAL/01'
TDT+20+00018N+1++GEK:172:87+++47AVS:103::SALERNO PRIDE'
RFF+VON:GKS01A'
LOC+165+ITSAL:139:6'
DTM+132:200907251430:203'
NAD+MR+RECEIVER-ID:160:87'
NAD+CF+GEK::172:87'
CTA+IC+BOOKING DPT:TEL.?+39 000 0000000'
EQD+CN++42G1:102:5++2+4'
RFF+CN:SAL/01'
EQN+1'
LOC+11+ITGIT:139:6'
MEA+AAE+G+KGM:4200'
TDT+1++3+31'
CNT+16:1'
UNT+18+2'
UNZ+1+1'