Fisheries VMS Domain · Lesson 1 of ∞
Orientation
The three-pillar model every fisheries-tech term you'll meet is a piece of — and where e-Boat sits inside it.
Start with the problem, not the acronym. Fish stocks are a shared, depletable resource. If nobody checks who is fishing, where, and how much, the resource collapses — that's the textbook tragedy of the commons at sea. IUU fishing (Illegal, Unreported, Unregulated) is the umbrella term for the ways that check fails: someone fishing where they're not licensed to (illegal), someone catching fish and not declaring it (unreported), or someone fishing a stock or area with no rules at all (unregulated).The "IUU" acronym bundles three legally distinct failures — worth keeping separate, since e-Boat's violation catalogue will eventually need to say which one it caught.
Every fisheries control system in the world — e-Boat included — exists to make that check possible at scale. The standard way to describe the system is MCS:
Source: FAO — Fishery Monitoring, Control and Surveillance (Chapter 8), the standard reference for this framework.
A ToR requirement is almost always one pillar wearing a requirement-ID costume. "Monitoring objects, map, tracks, geofences" (C-009..C-039) is Monitoring. "Violations: catalogue, capture, history" (C-052..C-065) is Surveillance acting on Control rules. Once you can place a requirement on this three-pillar map, its purpose stops being mysterious.
VMS (Vessel Monitoring System) is shipboard equipment that reports a vessel's position — usually by satellite — to a fisheries authority at a set interval. It's worth noticing what kind of thing it is: not just a GPS tracker, but a licence condition. In most regimes, carrying a working, transmitting VMS unit is a legal requirement to hold a fishing licence at all — see FAO's 2000 legal paper on satellite-based VMS, which frames it exactly this way.
VMS is easy to confuse with AIS (Automatic Identification System), which also broadcasts vessel position by satellite/radio. The difference is purpose and access, not technology:
A third instrument, ERS (Electronic Reporting System), is the electronic version of the paper catch logbook: it reports what was caught, not where the vessel is. VMS and ERS are separate obligations that a complete national system has to carry, sometimes in separate software. That split shows up directly in Ukraine's architecture: eFish (live since 2024) owns permits, logbooks and landing declarations — the ERS/licensing half — while e-Boat owns the live position map and violation detection — the VMS half. That's why e-Boat's README lists e-fish as an external REST consumer rather than something e-Boat re-implements.
| World practice term | e-Boat piece |
|---|---|
| VMS position feed | EBoat.Gateway — telemetry ingest and normalisation |
| Geofence / closed area check | EBoat.GeofenceEvaluator + PostGIS |
| Control rule (what counts as a breach) | EBoat.RuleEngine |
| Surveillance follow-through | EBoat.Notifications |
| ERS / catch logbook / licensing | e-fish (external system, not e-Boat) |
Full glossary of every term above, plus a few more: reference/glossary.html.
Something unclear, or want to go deeper on any term here? Ask the agent that built this lesson — it's your teacher for this workspace, not just a lesson generator.