Friday, 13 May 2022

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!?

Friday, 23 July 2021

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!

Thursday, 8 July 2021

Questions sent via email

Often I receive emails with questions about EDI. 

I do not answer to emails whilst will be more than happy to support and share through the dedicated forum which is available here

Get your subscriptions and feel free to make all your questions so we can share and be useful for the whole "EDI Community". 


Friday, 21 May 2021

Options to report VGM data for incoming export containers

One of the funniest things connected to the SOLAS regulation, is that terminals can report the VGM of incoming export containers in several ways. 

    1. The recommended option: VERMAS

VERMAS incorporates information on the Verified Gross Mass (VGM) of a packed container, the time, place and method of determination of the VGM, the responsible parties, and references required by the receiver to assign the VGM to his transactions. If terminals want to go for standard option then that's definitely the right choice.

    2. The alternative option: including VGM data to the Full-In CODECO

In order to comply SOLAS requirements, CODECO SMDG 16 maintained by SMDG, includes amendments for transmission of data specifying a container’s verified gross mass (VGM) according to SOLAS regulation 2,chapter VI, paragraphs 4-6. If terminals cannot handle VERMAS, that's a good option.

    3. The last option: sending VGM with a separate Equipment Status Change CODECO

If, for any reason, terminal needs to keep separate the VGM process and the Gate process and cannot handle VERMAS then sending a CODECO with BGM0101=999 (Equipment Status Change Report) is definitely a good option.

Each option has both pros and cons but now, the real question is: which option do you use?

Friday, 29 May 2020

EDI processes in a modern container terminal [video]

I'm very glad to host on my blog the video of Luc Castera, the founder of Octopi, about the EDI processes in a modern container terminal: have a look at it, because it definitely worth the time!

EDI For Container Terminals: An Overview from Octopi by Navis on Vimeo.

Saturday, 2 May 2020

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.

Friday, 27 September 2019

Standardization problems

Standardization is definitely a complicated process: tons of MIGs are available on the web but end users always find the way to create unpredictable variables to prevent a correct data processing.  

Recently, I'm struggling with an issue about the VAT number of freight forwarders/custom brokers reported into COREOR D00B: apparently, it's unclear if the nation code has to be included, as NAD02, in NAD segment when reporting the VAT number

In terms of message structure, that's the issue: 




Value reported in NAD02, is the target value to transcoding hence the prefix 'IT' makes a big difference when applying the mapping rules and the translation rules.

I'm quite interested in collecting feed-back about this topic: in case you are experiencing the same issue in your EDI environment, you can drop a comment here!