# Data Quality (/docs/data-quality) To make sure that all emission calculations and regulation values are correct, Emission+ tries to automatically check your report data for data quality issues. The system can be configured to notify the crew on board about severe quality issues via email. ## How to Use This Guide [#how-to-use-this-guide] This page explains the automated data quality checks run on your reports. Each check exists to catch likely reporting errors before they affect compliance statements (EU MRV, UK MRV/ETS, FuelEU Maritime, SEEMP). A **WARNING** means a value looks unusual and is worth a second look. A **FAILURE** means the data is very likely incorrect and should be corrected before the report is used for a statement. **Matching a message to this guide:** each remark you receive is shown as a header line — date/time, event type, operation mode, and a validation code in capital letters (e.g. TOTAL\_CARGO) — followed by the message text. Every section below shows what that header and message actually look like, so you can match the message you received directly to the explanation and advice underneath it. ``` 10.3.2026, 02:06 / DEPARTURE (OPM_PORT) / WEIGTHS_DISPLACEMENT The calculated displacement of 19860 does not match the reported displacement of 8730 mt. ``` ## Report Completeness [#report-completeness] These checks make sure every part of a noon or event report has actually been filled in and confirmed before it is used for compliance calculations or statements. ### Completeness [#completeness] Why am I told my report is "not completed"? A report has several sections: ROB, Cargo, Engine, Lube Oil, Nautical, Running Hours, plus each fuel consumption line. Every one of these must be ticked/confirmed. If even one section is left unconfirmed, the whole report counts as incomplete. MESSAGE YOU MAY RECEIVE ``` 12.6.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / COMPLETENESS Report from Fri Jun 12 2026 10:00:00 GMT+0000 is not completed. ``` What the vessel should check / change: * Open the report and check every tab — ROB, Cargo, Engine, Lube Oil, Nautical, Running Hours. * Make sure each section shows "Confirmed", not just "Saved". * Check that every fuel consumption line item is confirmed too, not only the section as a whole. ## Navigation and Position [#navigation-and-position] These checks cross-reference reported GPS positions, distances, speed and event timing against each other and against physics — most issues here come down to a typo in position or distance figures, or the wrong operation mode being selected. ### Distance / Minimum Distance / Maximum Distance [#distance--minimum-distance--maximum-distance] Why is my reported distance flagged as too short or too long? MESSAGES YOU MAY RECEIVE ``` 5.3.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / DISTANCE Previous position is lat: 53.982 / lon: 7.997 Current position is lat: 54.512 / lon: 8.221 The distance between the positions is 32.4 NM The theoretical maximum distance the vessel could have achieved according to its max speed is 288.0 NM. However, the reported distance is only 12.0 NM. ``` ``` 29.5.2026, 10:00 / NOON (OPM_MANEUVERING) / MINIMUM_DISTANCE Reported Distance over ground (16.0nm) is too short to make good distance of 46.0nm. Moved from 53.9817 LAT, 7.9967 LON to 54.0183 LAT, 9.2983 LON ``` ``` 18.2.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / MAXIMUM_DISTANCE The reported distance over ground is 320.0nm. However, the vessel could have achieved at most 288.0nm during the reported duration. ``` The system calculates the distance between this report's GPS position and the previous one, and compares it with the Distance Over Ground (DOG) you reported. It also checks that the distance is physically possible given the vessel's maximum speed and the time elapsed. What the vessel should check / change: * Double-check the latitude/longitude entered for this report — a typo here is the most common cause. * Double-check the DOG (distance over ground) figure against the deck log. * If the vessel genuinely traveled further/shorter than usual (e.g. weather routing, drifting), a brief remark in the report helps future reviewers understand it. ### Position [#position] Why is the distance between my current and previous position flagged? MESSAGE YOU MAY RECEIVE ``` 2.4.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / POSITION The distance between the reported coordinates [lat: 53.982 / lon: 7.997] and [lat: 55.812 / lon: 10.221] is 342.6 nm However, the theoretically possible distance is only 288.0 nm. ``` Similar to the Distance check, but based purely on the GPS coordinates of two consecutive reports rather than the reported DOG figure — it flags positions that would require an impossible speed. What the vessel should check / change: * Re-check GPS coordinates for both this report and the previous one. * Confirm the report date/time — an incorrect date can also make the implied speed look impossible. ### Arrival Port [#arrival-port] Why does my ARRIVAL report show a port position mismatch? MESSAGE YOU MAY RECEIVE ``` 10.1.2026, 06:00 / ARRIVAL (OPM_PORT) / ARRIVAL_PORT The distance between the reported position and the port's position is 68.412 NM. We expected a distance of 45 NM or less. Current Position is lon: 4.123 / lat: 51.912 Port Position is lon: 4.402 / lat: 51.955 ``` On confirmed ARRIVAL reports, the reported GPS position is compared against the known coordinates of the port (identified by its LOCODE). A large gap usually means the wrong port/LOCODE was selected, or your actual anchorage/berth is far from the charted port center. What the vessel should check / change: * Double-check the port and LOCODE selected in the report. * Confirm the reported GPS position matches where the vessel actually was at time of arrival. * If the vessel legitimately anchored far offshore awaiting berth, note this in the report remarks. ### Maximum Speed [#maximum-speed] Why is my reported speed over ground (SOG) flagged? MESSAGE YOU MAY RECEIVE ``` 22.7.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / MAX_SPEED Reported speed over ground 21.4 kn is higher then the specified max. speed of the vessel 16.5 kn Reported SOG should not exceed the vessel's configured maximum speed by more than 20%. ``` What the vessel should check / change: * Check the SOG figure for typos (e.g. an extra digit). * If the vessel was genuinely assisted by strong current, this can be noted in the remarks. * If strong current genuinely explains the gap, a remark helps clarify this for reviewers. ### SOG vs STW [#sog-vs-stw] Why is the difference between SOG and STW flagged? MESSAGE YOU MAY RECEIVE ``` 3.5.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / SOG_STW The difference between reported SOG 14.2 kn and STW 7.6 kn is 6.6 kn. ``` Speed over ground and speed through water are expected to be reasonably close. A large gap usually reflects a data entry error rather than actual current/tide effects. What the vessel should check / change: * Check both SOG and STW entries for typos. * If strong current genuinely explains the gap, a remark helps clarify this for reviewers. ### Duration [#duration] Why is the time between reports flagged? MESSAGE YOU MAY RECEIVE ``` 9.9.2026, 22:00 / NOON (OPM_SEA_PASSAGE) / DURATION The duration between the events needs to be greater 0 and less or equal to 26 hours. The reported duration is 32.0 hours. ``` The time between two consecutive reports should be greater than 0 and generally under 26 hours (30 hours is a hard limit). This usually means a report was submitted late, skipped, or the report date/time was entered incorrectly. What the vessel should check / change: * Check the reported date and time for the current and previous reports. * Make sure no report was accidentally skipped for the period in question. ### DOG at Anchorage [#dog-at-anchorage] Why am I flagged for making distance while "anchored"? MESSAGE YOU MAY RECEIVE ``` 14.1.2026, 10:00 / NOON (OPM_ANCHORED) / DOG_ANCHORAGE Vessel reported to be at anchorage. However, distance of 18.2 nm (17.4 nm per day) was made good. Acceptable distance for an anchorage-event is 5 nm per day. Please check operational mode (anchorage) and distance. Note: The reported operation mode (anchored, maneuvering, sea passage...) should always reflect the past period. If vessel has just dropped anchor, the past operation mode cannot be "anchored". ``` If the operation mode is set to "Anchored", the vessel is expected to have made very little distance (around 5 NM/day). This usually fires when the operation mode was set to "anchored" too early, while the vessel was still maneuvering into position. What the vessel should check / change: * Remember: the reported operation mode should reflect the period *before* this report, not the current instant. If the vessel only just dropped anchor at the end of the period, the mode for that period is not yet "anchored". * Check whether "Maneuvering" would have been the more accurate mode for part of the period. ### Event Cycle [#event-cycle] Why am I told an event was never "closed"? MESSAGE YOU MAY RECEIVE ``` 7.3.2026, 14:00 / ARRIVAL (OPM_PORT) / EVENT_CYCLE You have reported a new ARRIVAL event, however your previous ARRIVAL event at 3/5/2026, 9:00:00 AM has never been closed by an event of type DEPARTURE. Please note that ARRIVAL events always require a subsequent DEPARTURE event before reporting the same event type again. ``` Certain events must always be reported in pairs: * ARRIVAL → DEPARTURE * STS\_START → STS\_STOP * DOCK\_ARRIVAL → DOCK\_DEPARTURE * SHIFTING\_START → SHIFTING\_STOP * ANCHOR\_AND\_DRIFTING\_START → ...STOP * BOSP → EOSP * DP\_START → DP\_STOP * ENTERING\_CHANNEL → LEAVING\_CHANNEL This fires when the same event type is reported twice without its closing counterpart in between. It also checks that a DEPARTURE's port code matches the immediately preceding ARRIVAL's port code. What the vessel should check / change: * Check the sequence of recent events for the vessel — did a closing event get missed or entered with the wrong event type? * If a DEPARTURE port code doesn't match the prior ARRIVAL, check whether the wrong port was selected on either report. ## Engine Performance [#engine-performance] These checks compare running hours, energy, RPM and power against each other, since a running engine should always show consistent, non-zero values across all of these fields. ### AE Operation Hours [#ae-operation-hours] Why is an auxiliary engine flagged? MESSAGE YOU MAY RECEIVE ``` 11.6.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / AE_OPERATION_HOURS Validating running hours (0.0h) and energy (14 MWh) Running hours are zero but energy is non-zero. ``` For each auxiliary engine (up to 6), running hours and energy output are checked against each other. If hours are zero but energy is reported, or the engine ran for more than 1-2 hours but shows zero energy, this is flagged. What the vessel should check / change: * Check the running hours and energy (MWh) entries for each AE against the engine log. * A common cause is simply forgetting to fill in one of the two fields for an engine that was in use. ### Maximum Power [#maximum-power] Why is my main engine power flagged? MESSAGE YOU MAY RECEIVE ``` 19.6.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / MAX_POWER The reported ME power of 9800 kW is higher then the specified max. power of 8500 kW During sea passage, the reported main engine power should not exceed the engine's rated maximum continuous rating (MCR). ``` What the vessel should check / change: * Check the reported ME power figure against the engine log. * Confirm the vessel's MCR power is correctly set up in the vessel master data — if it looks wrong, flag it to your data administrator rather than the crew. ### ME Energy / ME Running Hours / ME RPM [#me-energy--me-running-hours--me-rpm] Why is my main engine flagged for running but showing no energy/RPM (or vice-versa)? MESSAGES YOU MAY RECEIVE ``` 23.6.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / ME_ENERGY No ME energy was reported even though ME was running for 22.5 hours ``` ``` 24.6.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / ME_RUNNING_HOURS No ME running hours have been reported even though ME Energy or ME RPM are not zero (ME Energy = 1840 kWh; ME RPM = 92 rpm) ``` ``` 25.6.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / ME_RPM ME rpm have been reported even though ME was running 22.5 hours ``` These three checks cross-verify that a running main engine also shows non-zero energy and RPM, and that non-zero energy/RPM is only reported alongside non-zero running hours. This usually means one field was accidentally left at zero. What the vessel should check / change: * Check ME running hours, ME energy (kWh) and ME RPM together — if the engine ran, all three should show a non-zero value. ### ME SFOC [#me-sfoc] Why is my main engine's fuel consumption efficiency flagged? MESSAGE YOU MAY RECEIVE ``` 30.6.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / ME_SFOC Reported SFOC 215.4 g/kWh is not matching the expected SFOC of approx. 189.2 g/kWh +/- 15% ``` The Specific Fuel Oil Consumption (SFOC, in g/kWh) is compared to a theoretical curve based on engine load, only for sea-passage reports of 10+ hours with a load between 10-100%. A gap of more than 10% triggers a warning, 15% a failure. What the vessel should check / change: * Check the reported ME load and ME energy figures — an error in either will distort the calculated SFOC. * If the engine genuinely runs less efficiently (e.g. due to fouling, poor fuel quality, weather), this is worth noting, but repeated large deviations are worth investigating mechanically too. ### RPM vs Power [#rpm-vs-power] Why is my main engine power flagged relative to its RPM? MESSAGE YOU MAY RECEIVE ``` 2.7.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / RPM_POWER The reported ME power of 7600 kW for 88 rpm is out of the expected power range of approximately 6100 kW. The deviation is 24.6 %. (MCR power: 8500 kW, MCR RPM: 95 rpm, RPM reported: 88 rpm) ``` For sea-passage reports, reported ME power is compared to the power expected for the reported RPM, using the standard propeller law (power roughly proportional to RPM cubed). Deviations beyond about -20%/+15% warn, and -30%/+25% fail. What the vessel should check / change: * Check both the reported RPM and power figures for consistency. * Confirm the vessel's MCR power and MCR RPM are set up correctly in master data. ## Fuel Consumption [#fuel-consumption] These checks make sure that reported fuel consumption lines up with what the vessel was actually doing (running engines, being in port, using shore power, etc.), and that consumption figures are internally consistent. ### Port Consumption [#port-consumption] Why am I flagged for zero auxiliary engine consumption in port? MESSAGE YOU MAY RECEIVE ``` 5.7.2026, 10:00 / NOON (OPM_PORT) / PORT_CONSUMPTION No A/E consumption has been reported even though vessel was not connected to shore power. ``` At DEPARTURE, or at a NOON report while in port, if the vessel wasn't connected to shore power and didn't use a shaft generator, some auxiliary engine consumption is expected — a vessel needs power from somewhere. What the vessel should check / change: * Check whether shore power or a shaft generator was actually used and correctly recorded. * If neither was used, check that AE consumption was actually entered for the period. ### Sea Consumption (AE & ME) [#sea-consumption-ae--me] Why am I flagged for zero consumption while at sea? MESSAGES YOU MAY RECEIVE ``` 6.7.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / SEA_CONSUMPTION_AE No A/E consumption has been reported even though vessel was not using shaft generator. ``` ``` 7.7.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / SEA_CONSUMPTION_ME No M/E consumption has been reported even though ME was running for 23.8 hours ``` While the vessel is genuinely underway (sea passage, maneuvering, anchored, drifting, STS), running hours for the auxiliary or main engine should correspond to non-zero fuel consumption for that engine. What the vessel should check / change: * Check the AE/ME consumption entries against the corresponding running hours. * For AE: if a shaft generator was used instead of an auxiliary engine, make sure that is recorded — otherwise zero AE consumption with zero shaft generator use looks like a missing entry. ### Gross/Net Plausibility & Gross vs Net [#grossnet-plausibility--gross-vs-net] Why are my gross/net consumption figures flagged? MESSAGES YOU MAY RECEIVE ``` 8.7.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / GROSS_NET_PLAUSIBILITY Implausible Gross/Net consumptions for HSFO/ME/1: net=-0.4000mt, gross=8.2000mt. Net consumption is negative! ``` ``` 9.7.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / GROSS_VS_NET Implausible Gross/Net consumptions for VLSFO/AE/2: net=5.1000mt, gross=5.6000mt. Difference between net and gross is 8.93% ``` Net consumption can never be negative, can't be zero when gross is non-zero, and can never be greater than gross consumption. Separately, if net and gross differ by more than 3-5%, this is flagged as implausible. What the vessel should check / change: * Check the gross and net consumption entries for the flagged fuel/engine combination. * Net should always be slightly less than or equal to gross (net accounts for losses, e.g. sludge) — never greater. ### Sludge Factor [#sludge-factor] Why is my sludge amount flagged? MESSAGE YOU MAY RECEIVE ``` 10.7.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / SLUDGE_ASSUMPTION Unrealistic assumption of sludge stock: Sludge factor of 3.42% for stock 1 exceeds maximum allowed value of 2% ``` The difference between gross and net consumption (i.e. the implied "sludge") shouldn't exceed 2% of gross consumption for any given fuel stock. What the vessel should check / change: * Check the gross vs net figures for that specific fuel stock — a large unexplained gap usually points to a data entry issue rather than actual sludge production. ## ROB, Bunkering & Corrections [#rob-bunkering--corrections] This is the most detailed group of checks. It verifies that Remaining On Board (ROB) figures are consistent with bunkering and consumption over time, that bunker delivery notes add up, and that soundings/corrections are done regularly. ### Fuel Cycle [#fuel-cycle] Why is my ROB flagged as not matching expectations? MESSAGE YOU MAY RECEIVE ``` 15.7.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / FUEL_CYCLE The difference between reported ROB [812.400mt] and expected ROB [809.900mt] is 2.500mt. Reported ROB of the previous report was 830.100mt, gross consumption was 17.700mt and 0.000mt were added by bunkering. ``` This is the core ROB check: previous ROB + fuel bunkered since then − fuel consumed since then (adjusted for any correction) should equal the newly reported ROB. A gap of more than 0.1mt warns, more than 1mt fails. What the vessel should check / change: * Check the ROB figures on this report and the previous one for typos. * Check that any bunkering between the two reports was recorded with the correct amount and date. * Check the consumption figures reported for the same period. ### Bunker POS Sum [#bunker-pos-sum] Why is a bunkering flagged for its attached POS (Proof of Sustainability)? MESSAGE YOU MAY RECEIVE ``` 20.7.2026, 12:00 / NOON (OPM_PORT) / BUNKER_POS_SUM Bunker BDN-4471 from 2026-07-18T00:00:00.000Z has attached POS that amount to 502.3mt, which exceeds its amount of 500mt. ``` Each bunkering can have one or more "POS" records attached. The sum of all attached POS amounts cannot exceed the total bunkered amount from the delivery note. What the vessel should check / change: * Check the individual POS entries attached to the flagged bunkering — their total should not be more than the BDN (bunker delivery note) amount. * In case the proportions of the fuel mix in terms of metric tonnes were calculated based on the energy content of the POS, you might have to manually adjust the POS amounts to match the BDN amount. ### Bunker POS Preliminary [#bunker-pos-preliminary] Why is a bunkering flagged as "preliminary"? MESSAGE YOU MAY RECEIVE ``` 20.7.2026, 12:00 / NOON (OPM_PORT) / BUNKER_POS_PRELIMINARY Bunker BDN-4471 from Sat Jul 18 2026 has an attached preliminary POS of 500mt with remark "awaiting final BDN". ``` This simply flags any fuel batch that is still marked as "preliminary" rather than finalized — a reminder that the entry needs to be confirmed once final figures are available. Emission+ **will not** consider POS fuels marked as preliminary as biofuels for the purpose of calculating the vessel's EU ETS and FuelEU compliance! What the vessel should check / change: * Follow up with whoever holds the final bunker delivery note figures and update the entry from preliminary to final. ### ROB Correction [#rob-correction] Why is a single ROB correction flagged? MESSAGE YOU MAY RECEIVE ``` 25.7.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / ROB_CORRECTION Reported ROB correction value for stock 1/HSFO of 12.500mt is 3.120% of the remaining value of 388.700mt. At least one reported correction is higher than 2.5% of the remaining value. ``` A single correction (from a sounding) shouldn't represent too large a percentage of the remaining stock — over 1% warns, over 2.5% fails. What the vessel should check / change: * Double check the sounding figures that led to this correction. * Large corrections on very low remaining stock can trigger this even for small absolute amounts — that's expected and less concerning than a large correction on a large stock. ### Correction vs Consumption & YTD Correction [#correction-vs-consumption--ytd-correction] Why are my accumulated corrections flagged? MESSAGES YOU MAY RECEIVE ``` 13.4.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / CORRECTION_VS_CONSUMPTION Gross Total Consumptions since last correction was 46.200mt. Correction is -3.000mt. The percentage difference of 6.5% is too large. The previous correction was 2026-04-12T10:00:00.000Z. ``` ``` 31.12.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / YTD_CORRECTION The total gross consumption across all fuels this year is 5120.400mt. The accumulated correction since the start of the year is -280.100mt. The percentage difference of 5.47% is too large. ``` Corrections made since the last correction (or since the start of the calendar year) are compared to total consumption in that same period. If corrections amount to more than 3-5% of consumption, this suggests a systematic reporting or measurement drift rather than one-off rounding. Additionally, if your vessel has made too large correction within a single calendar or scheme year, you might not be in compliance with regulation specific reporting accuracy requirements! What the vessel should check / change: * Review recent sounding practices — are soundings being done accurately and consistently? * If corrections are consistently in one direction (always up or always down), this points to a measurement or tank-table issue worth investigating. ### ROB Sounding [#rob-sounding] Why am I told sounding hasn't been reported recently? MESSAGES YOU MAY RECEIVE ``` 1.8.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / ROB_SOUNDING No sounding or correction of FO in the last 31 days reported. Note: Please report the sounding result as part of the daily ROB report. Tick the "Include Sounding" box at the top of the ROB report and enter the result at least once a month. ``` ``` 2.8.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / RECENT_ROB_SOUNDING There hasn't been a ROB sounding event since 34.0 days. Please perform ROB sounding soon. Note: Please report the sounding result as part of the daily ROB report. Tick the "Include Sounding" box at the top of the ROB report and enter the result at least once a month. ``` Every vessel is expected to physically sound its fuel oil and report the result (or a correction) at least about once a month. This check is a reminder rather than an error in the data itself. If you do not perform sounding regularly, Emission+ cannot verify the accuracy of your reported consumption values and might compute inaccurate emissions and compliance values! What the vessel should check / change: * Perform a physical sounding of fuel oil tanks. * When submitting the ROB report, tick the "Include Sounding" box and enter the result — this should be done at least once a month. ## Cargo [#cargo] These checks make sure cargo figures only change when they should (during port stays or STS operations), and that weight figures are internally consistent. ### Total Cargo [#total-cargo] Why is a change in cargo quantity flagged? MESSAGE YOU MAY RECEIVE ``` 10.8.2025, 10:00 / NOON (OPM_MANEUVERING) / TOTAL_CARGO Report: NOON OPM_MANEUVERING 2025-08-10T10:00:00.000Z Previous DWT carried: 5277 t, current DWT carried: 0 t Modifications to DWT carried occurring when the vessel was not in port and was not doing STS operations. Note: If vessel is anchoring within port limits for cargo operations, this is considered as a port stay and ARIVAL and DEPARTURE events have to be created. ``` Cargo quantity is expected to stay the same between reports, except around DEPARTURE/STS\_STOP events or while the vessel is in port, at STS, or docked. A change outside of these situations looks like an unreported cargo operation at sea. What the vessel should check / change: * Check whether a cargo operation actually took place, and if so, whether the correct event type and operation mode were used for that period. * Remember: if the vessel anchors within port limits specifically for cargo operations, this should be reported as a port stay with proper ARRIVAL/DEPARTURE events. ### Cargo Type [#cargo-type] Why am I flagged for missing DWT carried? MESSAGE YOU MAY RECEIVE ``` 12.8.2026, 10:00 / NOON (OPM_SEA_PASSAGE) / CARGO_TYPE DWT carried is missing in report. A general cargo ship has to report DWT carried for regulation specific logic. ``` General cargo vessels are required to report DWT (deadweight) carried in every report, as it feeds into regulation-specific calculations. What the vessel should check / change: * Make sure the DWT carried field is filled in for every report. ### Weight Displacement [#weight-displacement] Why is my displacement figure flagged? MESSAGE YOU MAY RECEIVE ``` 10.3.2026, 02:06 / DEPARTURE (OPM_PORT) / WEIGTHS_DISPLACEMENT The calculated displacement of 19860 does not match the reported displacement of 8730 mt. The difference of -11130 mt exceeds the allowable limit of 3150 mt. ``` The vessel's calculated weight (ROB fuels + fresh water + sludge + bilge water + cargo + ballast + the vessel's own lightweight) is compared against the reported displacement figure. A gap of more than roughly 20-30% of the vessel's lightweight is flagged. What the vessel should check / change: * Check the reported displacement figure against the vessel's stability/loading computer. * Check ROB, cargo and ballast figures on this report for possible errors — an error in any one of them can throw off this comparison. * If the vessel's "lightweight" setting is missing or looks wrong, flag this to your data administrator.