Category: Digital

For months we’ve been mining verified, publicly available EU MRV submissions at vessel level and turning them into something concrete: for each ship in your fleet, three cost drivers that compound simultaneously.

• Fuel-efficiency gap — what each vessel burns above its within-fleet median, priced per year ($).
• CII charter-rate exposure — the charter sensitivity of a deteriorating CO₂-intensity trajectory (a derived peer-band proxy, not an official IMO rating).
• EU ETS procurement savings — what forward-purchasing EUAs ahead of the September 2026 surrender is worth vs buying at the deadline.

Every figure comes back with a vessel name, a cause and a recommended action. No input required from your side for the first brief — we reconstruct it entirely from public data. The interpretation is ours; you just have to look at yours.

→ Get your fleet’s brief Run your company through the same pipeline and get a complimentary brief — fuel gap, CII exposure and ETS saving — in days, not weeks.

Figures are indicative; the peer band is a derived percentile of CO₂ intensity within the ship-type cohort — a commercial proxy for decision-support, not an IMO CII result or regulatory penalty.

Every vessel in the 2025 MRV book — 14,370 ships, 10 types, 3,736 operators — scored on real data, not a demo.

• See the band shape at a glance. Live A–E distribution per ship type, so you know where your fleet sits before you open a single file.
• Filter like an operator. Type, CII band, operator, percentile range, FuelEU 2030 status — or just type a name and hit enter. Sort on any metric.
• Open a vessel, get the story. CII band & percentile, CO₂ per nautical mile, P(D/E) risk score, charter sensitivity in $, ETS exposure, and FuelEU screening — plus its full 2021→2025 trajectory.
• Know your own fleet. Sister-fleet view groups same-operator × same-type ships and puts your percentile delta against them front and center — where you stand, not where the market does.
• FuelEU-ready. GHG intensity in g/MJ and a clean 2030 compliant / over-target read for every ship.

No build step. No spin-up. Load it, filter, click through — your fleet is one refresh away. → Check our dashboard

Since January 2024, maritime transport has been included in the EU Emissions Trading System (EU ETS). Ships within scope now have obligations to monitor, report, and ultimately surrender EU allowances for covered greenhouse-gas emissions. The phase-in is 40% for 2024 emissions, 70% for 2025 emissions, and 100% from 2026 emissions onward, with surrender taking place in the following compliance cycle. The geographical scope also matters: emissions are treated differently for voyages between EU/EEA ports, voyages between an EU/EEA port and a non-EU/EEA port, and emissions occurring while ships are at EU/EEA ports.

In parallel, FuelEU Maritime, Regulation (EU) 2023/1805, applies from 2025 and introduces a different compliance mechanism based on the greenhouse-gas intensity of energy used on board ships. Its requirements are expressed on a well-to-wake basis and become progressively more stringent over time.

And alongside the EU regimes sits the IMO’s Carbon Intensity Indicator (CII) framework. Since 2023, applicable ships have been required to calculate an annual operational CII and receive an A-to-E rating. A ship rated E for one year, or D for three consecutive years, must submit a corrective action plan showing how it will achieve a C rating or better.

These regimes overlap in their underlying operational data, but they are not three versions of the same calculation.

• EU ETS is an emissions-allowance regime.
• FuelEU is an annual greenhouse-gas-intensity and compliance-balance regime.
• CII is an IMO operational carbon-intensity rating regime.

That distinction matters.

A single voyage can generate data relevant to all three systems, but the resulting compliance calculations operate over different scopes, time periods, methodologies, and regulatory definitions.

The practical result is a data and software problem:

the same fuel-consumption and voyage records may feed several regulatory engines, but those engines cannot safely share the same assumptions.

Most operators still rely heavily on spreadsheets, manually maintained calculation tools, or internal systems whose regulatory assumptions are difficult to inspect and reproduce.

That is where a purpose-built calculation library can help—but only if the software treats the regulations as versioned rules rather than as a handful of constants.

Asset-integrity teams live with a recurring failure mode: a corrosion or remaining-life model arrives with impressive demo numbers, and then the conversation stops. What is the model actually doing? Is its rate within published literature for X65 carbon steel in atmospheric service? Does it hold up when you replay real survey history? Can your buyer’s engineer reproduce your numbers, not just trust a screenshot?

“Trust the vendor” is not a validation strategy. It’s how you get a surprise corrosion event three years after commissioning — and a very awkward conversation with whoever signs the integrity plan.

The Model Validation Framework (MVF) is a staged, evidence-producing pipeline that puts a degradation engine under test before it earns a seat in your integrity workflow:

Stage	Question answered	Evidence produced
S0 — Synthetic correctness	Does the engine do arithmetic?	Constant/noisy/step campaigns with exact expected outcomes; per-case pass/fail
S1 — Literature calibration	Are its rates defensible against published bands?	Every zone × material × rate cell checked against cited literature, PASS/FAIL per cell
S2 — Survey-record backtest	Does it replay history correctly?	Hold-out protocol: fit on survey history, predict the final survey; TTF hits, MAE, RMSE, Brier
S3 — Field campaign validation	Does it work on your licensed field data?	Same pipeline, same guarantees — campaigns ingest through a versioned schema and score identically

Two design decisions matter more than any metric:

1. The engine is imported as a pinned library. MVF does not fork, wrap, or “improve” vendor math. The report names the exact engine commit, so there is no ambiguity about what was tested.
2. Every report carries a provenance block — framework version, git SHA, engine commit, dataset checksums, config hash, run stamp — and is deterministic for a given stamp. A buyer re-running the pipeline gets byte-identical numbers. That sentence is the whole business case in miniature.

Or, Why Engineers Should Have What Software Developers Already Take for Granted

---

The Problem With Regulations

Marine engineering runs on regulations. MARPOL Annex I, IV, VI. SOLAS II-1, II-2. IACS Unified Requirements. Class rules. Flag state interpretations. EU MRV. CII ratings. The list is long and the list changes. A ship designed under this year’s regulations may be non-compliant before it leaves the builder’s yard.

Engineers know this. The problem is that compliance is not a moment — it’s a state. It has to be maintained across every drawing revision, every equipment substitution, every retrofitted scrubber, every re-route of a vent line.

And yet, the tools engineers use to manage this are largely the same ones they used twenty years ago: PDFs, spreadsheets, checklists, and a lot of institutional memory held in the heads of senior reviewers.

The Paper Problem

Every vessel subject to MARPOL Annex V must maintain a Garbage Record Book (GRB) — a chronological log of every piece of garbage generated, discharged, or incinerated at sea. In practice, this means paper forms that crew members fill out by hand, sign with a wet ink signature, and store in a binder that lives somewhere in the bridge.

The problems with this approach are well-known but rarely discussed openly:

• Illegible handwriting makes records difficult to verify during port state control inspections
• Missing signatures or incomplete entries create compliance gaps that can result in fines
• No automated compliance checking — crew don’t know a discharge is illegal until a port inspector tells them
• Hash chain integrity — paper records can be altered retroactively without detection
• No offline capability — many vessels still rely on paper because connectivity at sea is unreliable
• No audit trail — there’s no tamper-evident history of who changed what and when

The IMO’s 2023 guidelines on electronic record books acknowledge that digital solutions are permissible, but the industry has been slow to adopt. dGRB v2 is built to change that.

Getting started

The dGRB app is live at https://dgrb.ingeniat.eu — no signup required.

Demo account (frontend login):

• [email protected] / admin123 — admin role

How we built a production-ready anomaly detection system for marine diesel engines using scikit-learn, physics-based features, and an out-of-distribution detection layer.

---

Marine engine downtime costs shipping companies thousands per hour. A single unexpected failure — a seized bearing, a clogged injector, a cracked piston ring — can strand a vessel mid-voyage. Traditional monitoring systems rely on fixed thresholds: “if vibration exceeds X mm/s, raise an alarm.” But thresholds are brittle. They don’t adapt to operating conditions, they don’t catch novel failure modes, and they produce too many false positives to be useful at scale. That’s why we rebuilt our engine monitoring system from the ground up with a physics-informed machine learning pipeline that combines domain knowledge with unsupervised anomaly detection. Here’s how it works.

Port State Control (PSC) inspections can shut down a vessel for days. A single detention costs between $50,000 and $500,000 in delays, fuel, and reputation damage. Fleet managers spend weeks preparing for inspections using spreadsheets and gut feelings — but nobody actually runs the regulations against the ship’s real state.

What It Does

PSC Readiness is a compliance prediction platform that evaluates every MARPOL, SOLAS, and MLC requirement against a vessel’s actual design data, certificate status, and operational records — before inspectors arrive.

The app takes a vessel’s technical data and runs it through 265+ encoded regulatory rules and it produces:

• PSC Readiness Score — a single number indicating how clean the vessel is
• Predicted Deficiencies — specific items inspectors will flag, ranked by severity
• Risk Level — statistical prediction of detention probability
• Remediation Guidance — exactly what to fix and how

The BWM Suite just got a significant upgrade. Alongside the three core compliance calculators — D-2, Exchange, and Cost — we’re now shipping six new engineering tools designed for the people who actually operate, specify, and certify ballast water management systems.

These aren’t compliance checkers. They won’t tell you pass or fail in isolation. What they will do is answer the harder questions that sit behind the certificate: what’s really happening in your tanks, under your specific conditions, on your specific route?

Getting started

The BWMS Suite is live at https://bwms.ingeniat.eu — no signup required.

Demo account (frontend login):

• [email protected] / admin123 — admin role

---

What’s new

• TRO Decay & Neutralisation Planner — For operators running electrochlorination or ozone systems. Enter your initial dose, salinity, temperature, and hold time, and the tool maps out exactly when your ballast will drop below the 0.1 mg/L TRO discharge limit — and how much sodium thiosulfate or bisulfite you need if it won’t. Includes a 48-hour decay curve.
• UV Dose Calculator — For UV-based BWMS operators and BWMS specifiers. This one models the actual dose your system will deliver given lamp age, UV transmittance of the water, flow rate, and reactor geometry — then checks it against the D-2 required doses for bacteria, zooplankton, and the hardier algal cysts. It also tells you the maximum flow rate your system can handle while staying compliant.
• Type-Approval Envelope Analyser — The tool that answers “but will my BWMS work in these waters?” Every type-approved BWMS is certified over a specific band of salinity, temperature, and turbidity. This analyser overlays your route’s actual water quality parameters against that certified envelope and tells you exactly where you fall outside it — which matters when flag states ask for technical justification.
• Log-Reduction Uncertainty Propagation — Built for BWMS manufacturers and technical reviewers. Two systems can both be certified at 99.9% log reduction and have wildly different statistical margins. This tool propagates the measurement uncertainty from the type-approval test report through to the discharge concentration, giving you a probability of exceedance and a classification: Robust, Marginal, or High Risk.
• Tank Residual & Sediment Compliance Check — For shipowners on bulk carriers, tankers, or any vessel with tanks that can’t be pumped completely dry. It blends the treated ballast with the unpumpable residual — which still contains organisms at source concentration — and tells you whether the mix stays within D-2 limits at discharge. It also calculates the maximum allowable residual volume for your tank geometry.
• In-Tank Die-Off Estimator — The voyage planning tool. For each organism class — Enterococci, E. coli, zooplankton, phytoplankton, algal cysts — it applies first-order decay kinetics with temperature and salinity shock modifiers to estimate how many organisms survive to discharge. Algal cysts are effectively immortal. Everything else has a half-life. Now you can model it.

A note on the die-off estimator

The die-off estimator carries a prominent disclaimer: it is a planning tool, not a compliance record. No port state control authority in the world accepts natural mortality as a substitute for type-approved treatment or exchange. The tool exists to help you understand whether a longer voyage gives you a practical safety margin, not to game the system.

Managing ballast water compliance doesn’t have to be a spreadsheet nightmare.

The BWM Suite is a dedicated full-stack application for ship operators and maritime compliance teams to manage IMO BWM Convention requirements in one place.

Core Features

• Fleet Manager — Register your vessels with full technical specs (IMO number, GT, DWT, ballast capacity, tank count, BWMS type, installation date, certificate details). All fields editable. IMO numbers link directly to the vessel record for fast editing.

• Ballast Water Record Book — Log every ballast operation inline: date/time (UTC), position, tank ID, operation type (ballasting/deballasting), volume, salinity, source water, and treatment method. Supports CSV import/export for bulk entry. All data tenant-isolated.

• D-2 Calculator — Check discharge compliance against MEPC.200(62) D-2 organism count limits. Select BWMS type (Electrochlorination, UV, Ozone, etc.), source water salinity, discharge volume, and USCG waters flag. Returns pass/fail status, effectiveness percentage, and USCG approval flag.

• Exchange Calculator — Determines required exchange procedure (D-1 or D-2) based on voyage route, ballast volume, total capacity, BWMS status, and distance. Calculates exchange volumes for both 95% and 3× exchange methods.

• Cost Calculator — Estimates BWMS retrofit costs (low/mid/high) across five years including installation, consumables, and servicing. Gives cost per cubic metre and USCG approvability.

• Reports — Download a fleet-wide compliance summary as PDF or XML, or generate an IMO-style Ballast Water Record Book (PDF or XML) for any individual vessel.

Tech Stack

Backend: FastAPI + SQLAlchemy (async) + PostgreSQL, JWT auth via python-jose + passlib, PDF generation with ReportLab. Frontend: React + TypeScript + Vite, Nautilus design system, Axios with token refresh interceptor. 

Getting started

The BWMS Suite is live at https://bwms.ingeniat.eu — no signup required.

Demo account (frontend login):

• [email protected] / admin123 — admin role

 

Note: The BWM Suite was originally built as a standalone desktop-style application. It has since been reworked into a full client-server architecture with a dedicated FastAPI backend and PostgreSQL database, deployed as a separate service for demo purposes.

The compliance landscape for shipping has never been more complex — and the cost of getting it wrong has never been higher.

Fines under the EU ETS can reach €100 per tonne of CO₂ unaccounted for. FuelEU Maritime penalties stack annually. CII ratings that slip below C don’t just attract scrutiny — they attract commercial consequences: charterers route away, ports deny priority berthing, and insurance premiums climb.

And the regulations keep coming. New rules from the IMO, the EU Commission, and national authorities layer on top of each other every year. Staying current isn’t a one-time project. It’s a permanent operational function.

TideWatch is an automated maritime regulatory alert service that monitors the regulatory environment across nine major compliance regimes — and delivers the information you need, when you need it, where you already work.

Getting started

The deadline browser is live at https://tidewatch.ingeniat.eu — no signup required.

Demo accounts (frontend login):

• [email protected] / curator123 — curator role
• [email protected] / admin123 — admin role
• [email protected] / fleet123 — fleet operator role

Or explore the API directly:

• GET /api/deadlines?regulation=EU_ETS&region=EU&severity=CRITICAL
• POST /api/match with {"vessel_type": "cargo", "gt": 12000, "trading_area": "MEDITERRANEAN", "fuel_type": "VLSFO"}

---

Questions, corrections, or proposed new deadlines? Use the curator queue or open an issue. Every entry in TideWatch is reviewed by a human.

Nautilus is a fleet management and regulatory compliance platform designed for shipping companies, shipowners, and maritime consultants operating under IMO and EU environmental regulations. It centralizes vessel data, voyage records, and emissions calculations into a single backend, providing accurate, audit-ready compliance documentation for regulatory submissions.

The platform addresses the growing complexity of maritime environmental legislation — a landscape that has shifted dramatically with the introduction of the EU Emissions Trading System (ETS) for shipping in 2024, the IMO’s Carbon Intensity Indicator (CII) rating framework, FuelEU Maritime penalties, and theEnergy Efficiency Existing Ship Index (EEXI) certification requirements.

Try it now on https://nautilus.ingeniat.eu or check the specification here.

(Note: some features cut down on this demo version, contact us for access to a fully featured version)

Getting Started

Log in with the pre-filled credentials:
[email protected] / admin123

What Nautilus Does

Nautilus serves as the system of record for a fleet’s compliance posture. It tracks every vessel in a company’s register, records each voyage with cargo and consumption data, and calculates the resulting emissions, CII ratings, and EU ETS allowances automatically. The backend exposes a REST API consumed by a React frontend, with role-based access for fleet managers, company admins, and regulatory auditors.

Regulatory Calculations

The platform implements four interlocking compliance calculations:

EEXI (Energy Efficiency Existing Ship Index) — A theoretical maximum efficiency threshold calculated from a vessel’s technical design parameters (installed power, TTEW, DWT, design speed). Unlike operational ratings, EEXI is a design certification that vessels must meet through engine power limitations (EPL) or other technical upgrades. Nautilus stores the EEXI certificate reference and tracks compliance status per vessel.

CII (Carbon Intensity Indicator) — An operational rating expressed in grams of CO2 per cargo-carrying capacity per nautical mile (gCO2/t·nm). Vessels are assigned a rating from A (best) through E (worst) based on their annual operational performance. Ratings below D for three consecutive years trigger a corrective action requirement (CAP). Nautilus calculates the CII per voyage leg and aggregates it into a rolling annual rating per vessel.

EU ETS (European Union Emissions Trading System) — Shipping companies operating within EU ports must surrender EU Allowances (EUAs) covering 100% of CO2 emissions from intra-EU voyages and 50% from voyages arriving from or departing to non-EU ports (phased in through 2026). Nautilus tracks total verified emissions per voyage, converts to EUA requirements, and maintains an allowance ledger per company.

FuelEU Maritime — In effect from 2025, this regulation imposes a greenhouse gas (GHG) intensity limit on energy used on board vessels. The limit tightens progressively (‑2% in 2025, reaching ‑80% by 2050). Vessels exceeding the limit face penalties. Nautilus flags non-compliant voyages by comparing fuel energy content against the GHG intensity target.