Fisheries VMS Domain · Lesson 3 of ∞ · ← Lesson 2

Control, upstream

The legal ladder: why a state is obligated to run something like e-Boat at all

Four instruments, oldest to newest, each tightening the obligation. A ToR doesn't invent these requirements — it inherits them.

It's tempting to read a ToR's monitoring requirements as one customer's preferences. They're closer to the bottom of a stack of international obligations a state has already signed up to — the ToR is just the last, most concrete rung. Four instruments matter, in order:

  1. UNCLOS (1982)The UN Convention on the Law of the Sea establishes that a coastal state has sovereign rights over fisheries in its Exclusive Economic Zone, and — critically — that a flag state is responsible for the conduct of its own vessels wherever they fish. This is the root of "flag state duty": your vessels are your legal problem, everywhere.
  2. UNFSA (1995, in force 2001)The UN Fish Stocks Agreement makes flag-state duty concrete and enforceable: investigate alleged violations, report outcomes to the relevant regional body, apply sanctions severe enough to actually deter. A flag state that can't see what its vessels are doing cannot meet this obligation — which is the direct legal ancestor of "you must run a VMS."
  3. FAO Code of Conduct for Responsible Fisheries (1995)Voluntary, but the reference standard almost every national fisheries law and FAO-funded programme cites. Establishes that the right to fish carries the obligation to fish responsibly, and lays out MCS as the mechanism for making that obligation real rather than aspirational.
  4. PSMA (2016)The Port State Measures Agreement closes the loop from the other end: even if a flag state fails at monitoring, a port state can refuse to let a vessel suspected of IUU fishing land its catch. Flag-state monitoring (what e-Boat does) and port-state control (PSMA) are complementary, not redundant — a vessel that evades one still meets the other.

Sources: UN briefing on the Fish Stocks Agreement, FAO Code of Conduct for Responsible Fisheries, FAO PSMA overview.

Where the EU fits in

The EU's Common Fisheries Policy Control Regulation is a regional implementation of the same ladder, made concrete with numbers: VMS mandatory for vessels ≥12m, ERS mandatory for vessels ≥12m, AIS mandatory for vessels ≥15m. It's not a separate legal tradition — it's UNCLOS/UNFSA obligations translated into a specific regulatory regime. Useful as a reference point precisely because Ukraine's fisheries reform (eFish, and the e-Boat tender) is visibly converging toward this EU-style concreteness rather than staying at the level of international treaty language.

Source: EUR-Lex summary of the EU's fisheries control system.

Reading a requirement through this lens

Take a concrete example from e-Boat's own non-functional requirements: device-to-map latency ≤ 30 seconds. That number isn't arbitrary UX polish — it's downstream of the same chain: a flag state can only discharge its UNFSA duty to "immediately and fully investigate alleged violations" if its monitoring data is close enough to real time that an investigation can still catch the vessel in the act, not read about it a day later. Every NFR in this system is worth running through the same question: which rung of this ladder is this number actually serving?

Check your recall

Primary source for this lesson: FAO Code of Conduct for Responsible Fisheries — short, and the one document most likely to be referenced directly by a customer or FAO counterpart in conversation.

← Back to Lesson 2 · Lesson 4: tracker devices and the ingest pipeline →

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.