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.
Note: Requires Veslink Optimum and IMOS v7.11.5401 or later.
Collecting MRV Data with the Event ROBs Control
The Event ROBs control records ROBs for specific events and time frames. If you are looking to generate consumption category and berth event breakdowns, use this method. Collecting data via the Event ROBs control maps Event Types (also known as Reasons) to the IMOS Leg Delays/Events form, which then enables MRV reporting.
In order to start using this control, ensure the following:
Edit the Event Types by editing the Observed Distance element. Go to Custom Data Source and then add Berth Events as a comma-separated list.
Example: Loading,Discharging,Idle In Port (Load/Disch/Bunkering),Stoppage for Safety Reasons,Reduction for Safety Reasons,Owners Matters,Charterers Request,Canal/Strait Transit,Shifting to Berth/Anchorage
Ensure that the Event Types added in the Veslink configuration are also added to the IMOS Delay Reasons form.
Ensure that the following Berth Events are added to both areas:
Shifting to Berth
Shifting to Anchorage
From Last Berth to Sea/Anchor
The values from the Event ROBs control are imported into IMOS and, if the activities on the IMOS Leg Delays/Events form match the Event ROBs Event Types, the values are captured in Leg Delays/Events (or Berth Events).
Preparing Your MRV Report
At the end of the annual reporting period, to prepare your MRV data, do the following:
Click the form name to download EventROBsControlReportDef.form, which is a report definition you will use to create an MRV report in the IMOS Report Designer.
Import the report definition into the IMOS Report Designer.
Export the report to Excel or CSV.
Save and share the report to generate aggregated values for a verifier or EU THETIS-MRV.