How port agents watch the ships entering a zone, without refreshing a tracker
Ship agents need to know when a vessel reaches the anchorage, the pilot station or the berth. How a drawn zone and AIS positions turn into one alert per arrival.
Part of the guide Workflow automation
A port agent can be told automatically when a ship enters a zone by drawing that zone on a map once, listening to the AIS positions ships broadcast on a timetable, and comparing each ship's position with where it was at the last check. Only the ships that moved into the zone, or sailed straight through it between two checks, produce an alert. The agent stops watching a tracking screen and gets a message with the ship's name, type, size, speed and stated destination when it matters.
This is for ship agents, husbandry and crew-change coordinators, chandlers, bunker suppliers and terminal operations desks. It covers how to draw useful zones, what AIS does and does not give you, a made-up example, the mistakes to avoid, and the AI employee that does the watching.
Which zones are worth drawing
Agents care about a handful of thresholds where their work changes. Each one is a separate shape, or a separate flow when the people told are different.
- The outer anchorage. A ship entering it is about to wait. The agent confirms documents, berth window and crew needs.
- The pilot boarding area. Arrival is now hours away, not days. Launch, provisions and customs can be lined up.
- The berth or terminal. Alongside means crew changes, surveys and deliveries can start.
- Leaving. A ship that was inside the anchorage at the last check and is outside now has sailed for the berth, or left the port.
Draw each zone tightly around the water that matters. A loose shape catches passing traffic and fills the inbox with ships that were never coming in.
What AIS gives you, and where it is thin
AIS is the signal ships send with their identity, position, speed and heading. The Ships (AIS) block listens to a live stream over your area for 30, 60 or 90 seconds and keeps the last position heard for each ship, with its MMSI, name, IMO number, type (cargo, tanker, passenger, fishing and so on), speed, navigation status, destination, ETA, length and draught when heard.
A ship also sends its name and type only every few minutes, so in a short listen some ships come back as Not heard yet. You can keep or drop those. The destination and ETA are what the crew typed, so they can be out of date or written in an unusual way.
How the zone remembers
The Zone alert block is what turns positions into events. It remembers where each ship was at the last real run, recognised by its MMSI, and reports one of four things: entered or crossed, entered only, inside now, or left. Crossed uses the straight line between the last position and the new one, so a ship that went through a narrow pilot area between two checks is still caught. Each ship reported carries zone_event and its previous position.
A worked example (made up)
Say an agency in Rotterdam handles about a dozen calls a week and wants to know when its ships reach the pilot boarding area. It draws the area as one shape, sets the check every 15 minutes, keeps cargo ships and tankers, and adds a table of the IMO numbers it is appointed for.
| Check | Ships heard in the area | Entered the zone | Ours |
|---|---|---|---|
| 09:00 | 38 | 2 | 0 |
| 09:15 | 41 | 1 | 1 |
| 09:30 | 36 | 0 | 0 |
Made-up figures for illustration only.
Over that half hour the agent gets one message, at 09:15, for the one appointed ship that crossed into the boarding area. The other arrivals were filtered out because they were not in the agency's list. Without the filter the desk would have three messages and would still be reading them to find its own.
Mistakes that make zone alerts noisy or late
- Checking too rarely. Once an hour is fine for an anchorage that ships sit in for a day. For a pilot area a ship passes in under an hour, check every 15 minutes or rely on Crossed.
- A huge area. Ships listens to at most 5 boxes for an area. Draw the stretch of sea you need, not the whole coast.
- No filter on your own ships. Unless you need every arrival, match against your appointment list with Match with my table by MMSI or IMO.
- Trusting ETA as a fact. It is the crew's own entry. Use it as a hint and confirm with the master or the port.
- Testing the memory with test runs. Only real runs write the zone memory. A test run in the editor shows what would be reported but does not move it.
The AI employee that watches the zone
Build it once and it runs while the flow is live:
- Schedule: every 15 minutes, or every hour for an anchorage.
- Area of interest: the approaches to the port, drawn around the water.
- Ships (AIS): listen 90 seconds, keep cargo and tankers.
- Zone alert: Entered or crossed it, with the pilot boarding area drawn on its map.
- Match with my table: only ships found in your appointment list.
- Email or a Slack post to the operations desk.
What arrives is a short message per check, only when one of your ships entered: name, MMSI, type, length, speed, status, destination, the zone event and a link to the ship's page on a public ship tracker. Add Show on a map after Zone alert and the message also links to a map of where each ship was and where it is now. For a queue report instead of alerts, set Zone alert to Are inside it and send a row to a sheet every half hour.
Start from the template for ships entering a zone, then redraw the shapes for your own port.
Questions
Can I be alerted only about the ships my agency handles?
Yes. Put Match with my table after Zone alert and keep only ships whose MMSI or IMO is in your list of appointments.
Why did a ship I know arrived not trigger an alert?
Either it sent no position during that run's listen, or coverage near your port is thin. A longer listen helps for ships at anchor; Crossed catches ships that passed through between two checks.
How often should the check run?
Every 15 minutes for a pilot area or berth, every 30 to 60 minutes for an anchorage where ships wait for hours.
Does it show where a ship came from?
It shows the previous position from the last run and the destination the crew entered, not the full voyage history.