Faromo turns noon-report fuel and distance data into a period-based internal emissions record. It presents CO₂ and CII calculations, an approximate FuelEU CO₂-WtW indicator and an ETS estimate from a manually supplied EU-scope ratio, without claiming accredited-verifier output or platform submission.
IMO DCS addresses annual fuel consumption and related activity data; CII derives operational carbon intensity and an A–E rating; EU MRV covers voyage and annual verified greenhouse-gas reporting; and EU ETS applies route scope and allowance-surrender obligations. FuelEU Maritime is different again, assessing annual average well-to-wake GHG intensity of onboard energy and the compliance balance.
Faromo’s current aggregator maps noon-report fuel-oil and diesel consumption to HFO/MGO. It calculates vessel-type CII, produces an approximate CO₂-based WtW FuelEU value without CH₄ slip or N₂O, and applies the phase-in factor to CO₂ using a user-supplied EU-scope ratio. This internal summary does not replace a verified MRV/FuelEU report, a 2026 ETS allowance calculation or submission to THETIS-MRV, the FuelEU Database or GISIS.
When evaluating emissions software, asking “does it have CII?” is not enough. Vessel and route scope, fuel pathway, greenhouse-gas set, verification, deadline and submission channel must be verified separately for each regime.[1][2][3][4][5][6]
For applicable ships of 5,000 GT and above, collect each fuel type and specified activity data; compare annual attained CII with required CII and manage the A–E rating and any required corrective action.
For applicable vessels and EEA voyages, collect CO₂, CH₄ and N₂O together with fuel, distance, time and related parameters under the monitoring plan, then prepare the report for accredited verification.
Apply 100% coverage to emissions within ports and on intra-EU voyages and generally 50% to extra-EU legs, including CH₄ and N₂O alongside CO₂ from 2026.
Use every energy source, WtT and TtW CO₂eq factor, engine/pathway and slip data to calculate annual average intensity, then connect it to the target and banking, borrowing or pooling decisions.
Faromo’s current output supports data preparation and internal control. The final column shows what remains before statutory reporting.
| Regime | Statutory control | Current Faromo output | Data source | Current boundary |
|---|---|---|---|---|
IMO DCS / CII | Annual fuel and activity data; attained/required CII and A–E rating | CO₂, distance, DWT/GT capacity selection and vessel-specific CII rating for 12 ship types | Noon-report HFO/MGO + user-supplied capacity/vessel type | All fuel types, SEEMP linkage, Administration verification and GISIS submission are not completed in the current workflow. |
EU MRV | Voyage monitoring; annual CO₂/CH₄/N₂O report and accredited verification | Period fuel, distance and internal CO₂ summary | Noon report; BDN is checked only for a fuel-coverage warning | Per-voyage MRV scoping, CH₄/N₂O, monitoring-plan workflow and THETIS-MRV submission are absent. |
EU ETS | Allowance surrender obligation from verified in-scope GHG | User-supplied scope ratio × CO₂ × annual phase-in factor | Internal CO₂ total and manual 0–1 scope ratio | CH₄/N₂O required in 2026, automatic voyage scope, company aggregation and Union Registry workflow are absent. |
FuelEU | Complete WtW CO₂eq intensity, target and compliance balance | Approximate CO₂-based WtW indicator for HFO/MGO | Noon-report fuel mass + default LHV/WtT factors | CH₄ slip, N₂O, pathway/certification, OPS, full voyage scope, verifier and FuelEU Database workflow are absent. |
A single number labelled “MRV”, “ETS” or “FuelEU” does not establish compliance. The statutory result depends on applicable scope, complete GHG data, an approved monitoring plan and the authorized verification chain.
This control tests the move from software-produced calculations to a reliable statutory-reporting dataset. Maintain a separate acceptance record for each vessel and regime.[1][2][3][4][5][6]
Faromo’s current emissions record is a planning and data-coverage tool. It does not replace accredited verification, statutory platform submission or a compliance document.
Aggregate distance and HFO/MGO consumption for annual or quarterly periods within company and vessel scope.
Use the applicable DWT/GT metric, reference line and rating-boundary vector across 12 vessel types.
See a service-response warning when period BDN records contain fuel outside the HFO/MGO aggregator.
Produce an approximate CO₂-based WtW value for HFO/MGO using default energy and WtT factors, separated from the statutory CO₂eq result.
Apply the reporting-period CO₂ and annual phase-in factor to a user-supplied 0–1 scope ratio.
Move a draft into an internally verified state and produce vessel- or fleet-level internal summary PDFs.
HFO/MGO consumption and distance are aggregated by period to produce CO₂, vessel-type CII, approximate FuelEU CO₂-WtW and an ETS indicator from a manually supplied EU-scope ratio.
No. The current value is an approximate CO₂-based WtW indicator for HFO/MGO. Without CH₄ slip, N₂O, complete pathway/certification data, OPS and full voyage scope, it does not replace statutory FuelEU CO₂eq intensity or the compliance balance.
Not on its own. The current calculation relies on a user-entered scope ratio and CO₂. With CH₄ and N₂O entering ETS scope in 2026, verified MRV data, voyage scope and company aggregation are also required.
The current engine supports bulk carrier, tanker, container, gas/LNG carrier, general and refrigerated cargo, combination carrier, ro-ro cargo/vehicle/passenger and cruise passenger profiles. The correct vessel type and applicable DWT/GT capacity must be supplied.
No. The current service produces an internal report, stores an internal verification state and exports PDF summaries. It has no submission integration with THETIS-MRV, the FuelEU Database, Union Registry or Administration/GISIS.