Funny facts and BAPLIE file

It's funny to discover that, some facilities, are still not able to work with the BAPLIE file and use some complex EXCEL spreadsheet to capture and reporting the vessel stowage. 

Here below, the screenshot of a stowage plan entirely in EXCEL which includes very complex vbs scripts to summarize the discharge totals based on the port letter code:

 

 

I came across with it when a colleague contacted me to understand if any way to convert this file in a standard BAPLIE and could not believe my eyes!

Did you ever see something like this!?

Charge IMPORT STORAGE in a container terminal based on UN/EDIFACT files

If you work in a container terminal and you are in charge for invoicing processes, that's a very handy flow chart about where to retrieve sensitive info to charge import storage.

Hope it can be useful to you!

BAPLIE and flat rack bundle

Sometimes, the gap between MIGs and reality is definitely huge.

A good example comes from BAPLIE and flat rack bundle: here below, the correct way to report a bundle of flat in BAPLIE version 3. 

Sample comes from SMDG MIG which is available on the SMDG site or here.

Tricks when debugging an EDI transaction

Sometimes you might need to debug some EDI transactions and the lack of CR/LF can be an issue. I found out that Notepad++ can easly fix this issue:

But that's just the tip of the iceberg! I have developed a bunch of macros that can be used in a wide range of scenarios and that's a small sample: due to some internal procedures, I needed to remove the goods description into BAPLIE file but did not have the chance to edit related mapping rule. Goods description is stored in Segment Group 5 as FTX04:

FTX+AAA+++FAK OR CARGO  NOS WITH REFERENCE 998740013'

Applying the following criteria, in conjunction with CR/LF, will purge unwanted information and will change segment as follow: 

FTX+AAA+++'

                                    

Hope these tricks will be useful to you!

My best free tool for BAPLIE

In this post, I will review my best BAPLIE free tools available on the internet.

1. BAPLIE Viewer

It's a great and reliable tool developed many many years ago.

I know for sure that several small Terminals have used the BAPLIE Viewer as standard and unique ship planning program which may confuse you unless you never gave it a try.

BAPLIE Viewer has tons of functionalities; here below some of them: 

Files exported by the prgram:

• CSV comma separated
• TXT text files TAB delimited
• DBF, dBase IV file
• Microsoft Excel using preset template or to new worksheet
• Clipboard copy of data

Reports genrated:

• Container list, filtered and sorted
• IMDG list; list of dangerous cargo, filtered by port of discharge or displayed as transit cargo
• Reefer list; list of reefer containers; filtered by port of discharge and status (all, dry, live and empty reefer containers)
• Cargo summary; summary of all cargo on board by port of discharge
• Container data; selected container data from BAPLIE file
• Break bulk; summary of all break bulk cargo from BAPLIE file
• Suez canal report (cargo summary)
• Stack weight summary separate for deck and hold; 20FT, 40FT or mixed stowage
• OOG (Out of Gauge) containers summary with particular dimensions
• Container remarks; Handling instructions, Special instructions, Container remark, Description of goods, General information's

Statistics created: 

• General statistics; selection of different statistics per container type, operator, owner, etc...
• Tonnage sheet; break down of cargo by units and weight, operator, owner, container size, load and discharge port
• IMDG cargo summary; summary of dangerous cargo by class; port of discharge, container size, deck or hold
• Container type summary; different container types filtered by line operator
• Transversal weight distribution; weights and horizontal moments, calculation of cargo induced ship list
• Load port summary by operator; break down of cargo on board by operator, loading and discharge port

Additional tools and options:

• Decode and display content of BAPLIE file header
• Removal of line feeds and unprintable characters from BAPLIE file
• Create query to extract data from file
• BAPLIE file analysis; checking for different errors in BAPLIE file and/or stowage
• Bay view; graphical display of cargo stowage with different coloring filters
• Cargo plan; graphical display of cargo plan with different coloring filters
• ISO container types decoder
• ISO port codes; 8283 ports, automatically decoded for Baplie viewer, but can be used as separate routine
• Container Id check digit calculation

Support: 
BAPLIE 1.5, 2.07, 2.1, 3.0

Pros:
Tons of statistical reports;
Handy data export tool in several formats (including the Plan Master format).

Bay plan and letter plan printing;

Cons:

Not updated since 2005;
Does not validate message;
Does not support VGM.

2. EDIFACT Viewer

It's a great tool which supports not only BAPLIE but also several UN/EDIFACT messages.
Here the full list of supported messages. 
The EDIFACT Viewer allows to export messages in csv and html files plus has a very intuitive GUI to menage the contents of your files.

Support: 

All BAPLIE versions; 

Pros:

Easy to use; 
Solid message translation/acknowledgment; 
Support to VGM; 
Also tested on several Linux distros with Wine.

Cons:
The last updated version was released in 2010;

Does not validate message.

3. SVM BAPLIE Viewer

It's a very recent development which requires java in order to run on your pc.
SVM BAPLIE Viewer also validates the file and lets you know if there are any incorrect or missing segments which may prevent the file from being read and converted.

SVM BAPLIE Viewer allows to create customized data export templates which include the count function: template then can be saved on your pc and used as soon as you need it. 

Support:
SMDG15/BAPLIE 1.5, SMDG20/BAPLIE 2.0, SMDG22/BAPLIE 2.2 and SMDG31/BAPLIE 3.1.

Pros:

Customized template to export data;
Allow to handle data in pivot table style;
Support to VGM.

Cons: 
Requires an old and unsafe java version (Java JRE 1.6).

The impact of SOLAS on BAPLIE

VGM can be sent from Terminal operator via BAPLIE file.

That's a sample built on BAPLIE version 3.1 which is the very last stable version. This message version may be used to transmit data about VGM of containers. Usage of the according data elements is optional and needs to be agreed between communication partners. This message version provides for transmission of:

• Indication whether a specified gross mass has been verified or not
• Additional information providing evidence of verification.

(...)

LOC+147+0010082:9711:5'

EQD+CN+SUDU1234569:6346:5+42G1:6346:5+++5'

NAD+CF+OOL:LINES:306'

MEA+AAE+VGM+KGM:23780'

RFF+BN:SGSIN00002'

FTX+AAY++SM1:VGM:306+201606211600UTC:CWC LTD; PO BOX 987; CITY;?+1526888999:JOHN SMITH;WEIGHT MASTER EAST GATE:JOHN SMITH:US'

(...)

Note here below related codes: 

c107.4441 

SM1= SOLAS verification method used

c107.1131 

Verified Gross Weight

c108.4440 

201606211600UTC= Data/Time weight verification

c108.4440 

CWC LTD; PO BOX 987; CITY;?+1526888999= Data/Time when issued weighing party

c108.4440 

JOHN SMITH;WEIGHT MASTER EAST GATE= Contact Address Responsible Person

c108.4440

JOHN SMITH= EDI Signature

c108.4440

US= State where verified

It's also possible to state the verification document reference with the code DRF as c107.1131:

(...)

LOC+147+0010082:9711:5'

EQD+CN+SUDU1234569:6346:5+42G1:6346:5+++5'

NAD+CF+OOL:LINES:306'

MEA+AAE+VGM+KGM:23780'

RFF+BN:SGSIN00002'

FTX+AAY++DRF:VGM:306+201606211600UTC:JOHN SMITH:WEIGHT MASTER EAST GATE:DOCUMENT-ID'

(...)

Samples come from SMDG MIG: I have uploaded it here for your findings.

Restow in BAPLIE file

Some days ago I received the following complaint from an EDI customer:

"However everytime we receive a departure BAPLIE from your Terminal, where we have performed restows, we always get the restowed units showing as loaded from your port which clashes with the restowed unit."

In the beginning, I thought to have messed up some mapping rules but after having a look at the config file I realised that, at my end, everything was set-up properly. 

Here is the EQD segment group concerning a unit restowed by my Terminal:

(...)

LOC+147+0250208::5'
MEA+WT++KGM:6960'
LOC+9+ITSAL'  >> Place/port of loading
LOC+11+PTLEI' >> Place/port of discharge
LOC+83+PTLEI' >> Place of delivery (by on carriage)
LOC+76+ILHFA' >> Original port of loading
RFF+BM:1'

EQD+CN+ABCD1234567+22G1+++5'
(...)

I guess that customer's EDI translator has some issues in handling OPOL (Original Port of Loading) in conjunction with POL (Port of Loading): of course that's not up to me and, at least once, I was happy to close the support request without changing anything ! 

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'
(...)

BAPLIE and 11-tiers on deck

Life goes on and Shipping Lines are going to maximize their profit by using vessels bigger then ever.

Vessels with up to 11-tiers on deck may create some issue with the BAPLIE file: according the ISO recommended numbering the tier on deck should start from 82; this would mean that in case of 10th or 11th tier the corresponding ISO format should be 100 or 110.

Unfortunately, in the current cell position format, the tier number cannot exceeds the two digits; this brings me to the next question: how are you handling this issue in your working environment ?

It was told me that, in order to overcome this issue, some Carriers decided to start the tier numbers on deck not with 82 but with 62 but what about you ?!

BAPLIE for rail

In North Europe BAPLIE is also used to transmit, to the Rail Terminal Operator, infos about all railway wagons in a train.

Here below you can find a message sample based on SMDG's MIG (Version 0.1): that's a DRAFT version (still to be discussed) but, in my opinion, it's the right way to start !

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090211:0300+0001'
UNH+0001+BAPLIE:D:95B:UN:SMDG10'
BGM+746+0001+9'
DTM+137:0902110500:201'
TDT+20+11E+++GEK:172:ZZZ+++GTS01:ZZZ:ZZZ:POLAR EXPRESS:IT'
LOC+5+ITNOL:139:6'
LOC+8+ITSAL:139:6'
DTM+132:0902110730:201'
DTM+136:0902110500:201'
LOC+147+01+218333585907+01'
FTX+AAA+++TOMATOES'
MEA+WT++KGM:22500'
LOC+9+ITNOL:139:6'
LOC+11+ITSAL:139:6'
RFF+BM:1'
EQD+CN+GEKS1504090+22G1++3+5'
NAD+CA+GEK:172:ZZZ'
UNT+17+0001'
UNZ+1+0001'

Some comments about 'Stowage Cell':

• C517.3225: That's the first wagon in the train after the locomotive (01);
• C519.3223: That's the wagon numer as painted on the wagon (218333585907);
• C553.3233: On the wagon each 20FT slot has a number (01, 02...). In the sample container is allocated in the first slot (close to the locomotive).

BAPLIE: further comments

In the previous BAPLIE sample there is the following Stowage Instruction:

• Container: GEKS1504090 (LOC.EQD segment as c237.8260);
• Stowage Position: 0010112 (LOC.LOC segment as c517.3225);
• Main-Carrige Transport: Vessel SALERNO PRIDE (TDT.TDT segment);
• Loading Port: Cagliari (LOC.LOC segment as c517.3225);
• Discharging Port: Salerno (LOC.LOC segment as c517.3225).

There are also other interesting infos into the file and I would suggest to use the BAPLIE Viewer in order to retrieve them.

BAPLIE is also used to give infos about Breakbulk cargo loaded onto vessels; let's have a look at the next sample to understand the way it works:

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090211:0811+0001+++++GEKU'
UNH+0001+BAPLIE:D:95B:UN:SMDG20'
BGM++0001+9'
DTM+137:0902110811:201'
TDT+20+00018NB+++GEK:172:ZZZ+++47AVS:103:ZZZ:SALERNO PRIDE:IT'
LOC+5+ITCAG:139:6'
LOC+61+ITSAL:139:6'
DTM+132:090211:101'
DTM+178:0902111230:201'
DTM+136:0902112330:201'
RFF+VON:GKS01A'
LOC+147+0010112::5'
FTX+AAA+++LARGE VEHICLE'
MEA+WT++KGM:32500'
DIM+1+CMT:890:250:220'
LOC+9+ITCAG:139:6'
LOC+11+ITSAL:139:6'
RFF+BM:1'
EQD+BB+NY20978ZZ'
NAD+CA+GEK:172:ZZZ'
UNT+20+0001'
UNZ+1+0001'

I have added a couple of extra infos in order to deal properly the Breakbulk:

• Element 8053 on LOC.EQD segment now is BB (Breakbulk);
• On LOC.DIM segment there are off-standard Breakbulk dimensions; in detail:
  890 cm over-length, 250 cm over-width and 220 cm over-height.

BAPLIE

Purpose of the message: BAPLIE is used to transmit infos about all occupied places onboard of a vessel. Although the message can also transmit infos about 'empty places', this feature is not generally used.

Parties involved: Tonnage Center, Shipowner, Terminal operator.

The way it works: Generally BAPLIE is transmitted to the terminal operator of the next vessel call to retrieve all the relevant infos. Subsequently:

• Infos about equipment discharged will be removed;
  
• Infos about equipment loded will be added;
  
• Location about equipment shifted will be changed.
  

At vessel's sailing time, updated BAPLIE will be transmitted to: shipowner, tonange center and terminal operator of the next vessel call. Generally message is also transmitted to the vessel in order to replace the 'paper' master-bayplan.

Infos about 'Remain On Board' (i.e. equipment not handled during discharge/load operations) must remain unchanged and then transmitted to the next vessel call.

Here below a sample of a BAPLIE file 2.0.7. Here you can download the corresponding MIG.

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090211:0811+0001+++++GEKU'
UNH+0001+BAPLIE:D:95B:UN:SMDG20'
BGM++0001+9'
DTM+137:0902110811:201'
TDT+20+00018NB+++GEK:172:ZZZ+++47AVS:103:ZZZ:SALERNO PRIDE:IT'
LOC+5+ITCAG:139:6'
LOC+61+ITSAL:139:6'
DTM+132:090211:101'
DTM+178:0902111230:201'
DTM+136:0902112330:201'
RFF+VON:GKS01A'
LOC+147+0010112::5'
MEA+WT++KGM:22500'
LOC+9+ITCAG:139:6'
LOC+11+ITSAL:139:6'
RFF+BM:1'
EQD+CN+GEKS1504090+22G1+++5'
NAD+CA+GEK:172:ZZZ'
UNT+18+0001'
UNZ+1+0001'