Skip to main content
Skip table of contents

Veslink - MRV Reporting

Veslink standardizes voyage communications to help you collect and analyze current positions and other critical voyage data and share information with a network of trusted partners.

As of January 1, 2018, the European Union (EU) Shipping MRV Regulation requires monitoring, reporting, and verification (MRV) of CO2 emissions by shipping companies. For voyages that involve commercial ships exceeding 5,000 GT that call to EU ports and load or discharge cargo, MRV data must be shared annually with the EU.

The combined solution of Veslink and IMOS enables your organization to extract enough data to comply with the European Union's MRV reporting requirements. Although each shipping company is obligated to abide by the same MRV requirements, how each company chooses to fulfill these requirements may differ. The difference can be based on either:

  • The data collection and reporting systems used.
  • The accredited verifier selected.
  1. Collect berth consumption data, using either:
  2. Prepare your MRV report and then submit to your verifier.

The Veslink MRV Reporting solution exactly calculates berth consumption by event.

Berth events are specific events at berth, such as shifting to berth and shifting to anchorage. On the Statement of Facts form, these are essentially the port activities; on both the Statement of Facts form and the Event ROBs control, the berth events can be customized to meet the requirements of your verifier.

The Berth Events method provides more granular berth consumption tracking that certain verifiers require for MRV reporting. This method may be more seamless if you are already using the Statement of Facts form or can easily integrate the Event ROBs control, which was built for berth event breakdowns. Both data collection methods are mapped to IMOS event ROBs, which results in the ability to report by berth event.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.