FlowsBook a callSign inCreate free accountSign up
Workflows by industry

Ship tracking alerts for a port: what to watch, how often, and where the signal is thin

Setting up ship tracking alerts for a port: pick the event that matters to your desk, test the coverage first, choose the listen time, and know what a missed ship means.

Part of the guide Workflow automation

By the xMap team · · 5 min read

Ship tracking alerts for a port work best when each alert answers one desk's question: a ship arrived at the anchorage, a ship came alongside a berth, a cruise ship is heading in, a fishing boat entered a closed area. Listen to the AIS signals ships broadcast over the water you care about on a timetable, remember where each ship was last time, and send a message only when a ship does the thing that desk cares about. Before you rely on it, test how well your port is covered, because AIS reception varies a lot from coast to coast.

This guide is for port operators, agents, chandlers, bunker suppliers, tour operators, coast authorities and anyone else who needs to know about ship movements without watching a tracker all day. It covers the alerts different desks need, the coverage question, how often to check, a made-up setup at two ports, the mistakes to avoid and how to run it as an AI employee.

One alert per desk

WhoWhat they want to hearHow to set it
Berth plannerShips waiting at the anchorage, and when one leaves for the berthShips stopped in the anchorage area; a zone that reports ships that left
Terminal operationsA ship came alongside or left berth 4A small zone around the berth, reporting ships that entered or left
Chandlers and bunker salesWhich ships are at anchor now, with size and destinationStopped ships, every hour, posted to a sales channel
Tourism and city desksCruise ships on their way, with arrival timePassenger ships whose stated destination is the port
Coast and fisheries authoritiesFishing boats entering a protected areaFishing vessels only, a zone over the reserve

Each desk gets its own flow and its own channel. Mixing them makes every message longer.

Test the coverage before you trust it

AIS is a radio signal picked up by receivers along the coast. Where there are many receivers, almost every ship is heard; where there are few, many ships are missing. Busy European ports are heard well. Parts of the Gulf and the Red Sea are barely covered today. Elsewhere it varies by stretch of coast, and the only reliable way to know is to listen for a few days and compare with what you know is in port.

  • Run a test listen at different times of day and count the ships heard against the port's own arrivals list or what you can see.
  • Note how many come back without a name or type yet: ships send their name only every few minutes, so a short listen catches positions before names.
  • If the area sends nothing at all, the step says so. Treat that as a coverage gap, not an empty port.

How long to listen and how often to check

Ships are heard through a live stream, not looked up in a list: a ship that sends nothing while the flow listens is missed that time. Moving ships report every few seconds; ships at anchor or moored report only every few minutes. So the listen length matters most for anchorages: 30 seconds is enough for traffic under way in a busy channel, 90 seconds hears more of the ships at rest.

How often to check depends on how fast the desk must react. Every 15 minutes suits a terminal watching a berth. Hourly suits sales and anchorage counts. Once each morning suits a tourism desk planning the day. Because the flow remembers each ship's last position, a ship that went straight through a zone between two checks is still caught by the line from its last position.

A worked example, made up

A ship supplies company serves vessels at two ports, Antwerp and Santos. It wants its sales team told every hour about ships at anchor, and its operations team told when a ship it is supplying leaves the anchorage.

After a week of test listens, Antwerp is heard well: the counts match what the team expects. At Santos, many ships at anchor come back without a name in a 30-second listen, so the team moves Santos to 90 seconds and accepts that a few ships will still be missed some hours. The sales channel gets one post an hour per port listing ships stopped at anchor with their size and destination. The operations flow compares each ship with the company's own list of ships it supplies and reports only those that left the anchorage. Every figure here is invented.

Mistakes to avoid

  • Drawing the area too big. A wide box catches every passing ship and makes the message long. Draw tightly around the anchorage, the channel or the berth.
  • Treating a missing ship as absent. No signal is not proof a ship is not there, especially at anchor or on a thinly covered coast.
  • One alert for everyone. A chandler and a terminal planner want different things. Separate flows keep each message short.
  • Testing only once. Coverage changes with time of day and receivers going on and off. Test over several days.
  • Expecting the first run to be quiet. On the first run there is no memory, so every ship inside counts as entered. Ignore the first message.

The port watch as an AI employee

In xMap Flows a port alert is a short flow:

  1. Schedule: every 15 minutes, every hour or every morning, as the desk needs.
  2. Area of interest: the anchorage, channel or berth, drawn on the map.
  3. Ships (AIS): listen for 30, 60 or 90 seconds; keep the kinds of ship the desk cares about, moving or stopped.
  4. Zone alert: report the ships that entered, crossed, are inside or left the zone since the last run.
  5. Match with my table, when you need it: keep only ships on your own list, by MMSI.
  6. Email, Slack or WhatsApp: each ship with its name, type, size, speed, destination and position.

The template Ships entering my zone is the base flow, Ships waiting at anchor, for the berth planner counts the queue, and Cruise ships arriving at the port serves a tourism desk. More on operations work handled by AI employees is on the field operations page.

Questions

Why are some ships missing from the alert?

AIS is heard only where there are receivers, and only from ships that transmit during the listen. Ships at anchor report less often, so a longer listen hears more of them.

Why do some ships have no name?

Ships send their name and type every few minutes, less often than their position. In a short listen some come back as not heard yet.

Can I watch only my own ships?

Yes. Keep a table of their MMSI numbers and match each ship heard against it, keeping only yours or only the others.

Does it work in every port?

Coverage varies by coast. It is good in busy European ports and thin in parts of the Gulf and the Red Sea. Test your port before relying on it.

Templates that do this

Read next

More on workflows by industry · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.