Data Architecture - Validation

Introduction

Currently Vessel Master Domain (VMD) holds details on all Maersk owned and operated vessels as well as vessels in VSA agreements and feeders (around 7000 vessel entries).

It is proposed that VMD is expanded to include vessels used in all portfolios and platforms - for example SCP (MbM) and Landside (TbM), where the vessels are operated by other carriers, which may not exist in VMD at the time of the transaction. These vessels will have a limited set of required master data.

• In SCP cargo can be booked on vessels according to customer instructions or customer contracts.
• In landside there is requirement to hold details of discharge vessel (for start of landside) or load vessel (at end of landside)
• In APMT there is requirement to hold vessel details for all vessels that may call at APMT port.

Consider to introduce a ‘vessel validation’ component to VMD, to call external provider API (example Lloyds Register) with an IMO number - which would return key information about the vessel ( Flag, build date, name, etc) for any new vessel added to VMD solution. This would be used for non Maersk owned/operated vessels, and would ensure good data quality.

example → https://www.lr.org/en/about-us/who-we-are/lr-ships-in-class/