TPFREP [Pool]

ISO 6346

ISO 6346 is an international standard covering the coding, identification and marking of intermodal (shipping) containers used within containerized intermodal freight transport. 

The standard establishes a visual identification system for every container that includes a unique serial number (with check digit), the owner, a country code, a size, type and equipment category as well as any operational marks. 

The standard is managed by the International Container Bureau (BIC).

Here you can find a very useful page on wikipedia. 

TPFREP [Segment Group-3 DTM/FTX]

In TPFREP EDI message, the Segment Group-3 DTM/FTX is used to report vessel operations and handling times. 

Here below a sample: 

(...)
DTM+HLD:0052:401'
FTX+ZZZ+++OPENING / CLOSING HATCHCOVERS'
DTM+UCC:0018:401'
FTX+ZZZ+++LOADING OOG'
DTM+MSC:0300:401'
FTX+ZZZ+++CRANE BREAK DOWN (MECHANICAL)'
(...)

I have here enclosed a list with the following data elements currently implemented in my facility: 

• C507.2005 in DTM segment;
• C108.4440 in FTX segment. 

I hope that this can be useful to you. 

Code search application

One of the most annoying thing, when making an interchange agreement, is to find related customer identification codes.

I have developed a small application which collects the following standard identification codes:

• BIC;
• SCAC (not all); 
• SMDG. 

You can download it here.

Enjoy!

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.

Container ISO Codes

Today a new customer submitted me a COPRAR file for test purposes.

The file was plenty of ISO codes that had never seen before; same samples: 

•  2EGP
• LNP9
• EETN

In order to apply the COPRAR to my test DataBase I had to enter all the new ISO codes.

Time ago I found out, on SMDG web site, a very simple but effective program which was able to determine for all ISO codes the Lenght, Height, Width and Description.

The program is named Sity: it's developed only for Windows XP 32 bit.

I have uploaded it here in case you need it !

Date/time in EDI message

An UN/EDIFACT message contains several references to date/time but, first of all, you will find date/time into the UNB segment as S004.0017  / S004.0019:

    UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090730:1323+1'

This data/time identifies when the full interchange was generated and it's a good practice to use the UTC format. 

UTC date/time allows to determine exactly when the interchange was generated without converting local date/time of the sender into local date/time of the receiver. 

For instance: 

    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'

    (...)

This interchange was generated on the 2009/07/30 at 13:23 hrs UTC but the local date/time of issue of the first document is 2009/07/30 at 15:23 hrs. It's reasonable to assume that the sender of the message lives in a GMT+2 time zone.