How to Evaluate a Vessel Tracking Platform

Most tracking platforms look identical in a demo. Here is what actually separates them, what “satellite AIS” means in practice, and the questions to take into a vendor call.

Every vessel tracking platform shows ships on a map. In a demo, they all look capable, they all have alerts, they all have history, and they all have an API. Two months after signing, the differences become obvious, usually in the form of a vessel nobody could find, an alert nobody received, or a support ticket nobody answered.

This guide is about closing that gap. It sets out where platforms genuinely differ, where they do not, what the phrase “satellite AIS” actually commits a provider to, and how to choose an AIS platform for vessel movement monitoring before you commit rather than after. There is a printable checklist at the end.

Why evaluations go wrong

Two habits cause most of the damage.

The first is the feature checklist. Requirements get assembled into a spreadsheet, vendors tick the boxes, and everyone scores highly because almost every box is technically true. Checklists reward breadth of claim, not depth of capability, and they systematically fail to distinguish a feature that exists from a feature that works under pressure.

The second is the vendor-run demo. A demo uses the provider’s chosen vessels, in the provider’s chosen area, on a good day. It is a sales asset, not an assessment. Nothing in it tells you how the platform behaves with your fleet in the waters you actually operate in.

A better evaluation starts somewhere else entirely: with the decisions your team needs to make, and whether the platform helps them make those decisions faster.

Start with the decision, not the feature

Before speaking to any vendor, write down the three to five questions your team asks most often. They usually look like this. Where is this vessel, and is it running to plan? Has anything happened overnight that needs attention this morning? Why was this vessel late, and can we evidence it? Is anything of ours near a situation we should be worried about? What happened during this voyage, six months after the fact?

Those questions are your evaluation criteria. Every capability discussion should trace back to one of them. A feature that does not serve any of them is not a reason to buy, however impressive it looks.

What “satellite AIS” actually means

Satellite AIS integration appears in almost every provider’s materials and is one of the least examined claims in the market. It is worth unpicking, because the phrase commits a vendor to far less than buyers assume. You can find AIS Glossary here.

AIS was designed as a line-of-sight VHF system for ships to see each other. Terrestrial receivers pick it up reliably to perhaps 40 to 60 nautical miles from shore. Beyond that, coverage depends on satellites carrying AIS receivers, and satellite reception behaves differently from terrestrial reception in ways that matter operationally.

The four questions that separate the claims

How often is a given vessel actually seen? This is the revisit interval, and it varies enormously with constellation size, latitude and traffic density. A provider quoting an average is quoting a number that may not describe your trading area at all. Ask for the typical interval for a named vessel in the waters you operate in, over a week.

Whose satellites, and how many? Some providers own constellations, most buy access, and several resell the same underlying data. This is not a criticism; it is normal, but it means “satellite AIS” is not a differentiator on its own, and two platforms may be showing you identical positions.

Is it included, and for which vessels? Satellite AIS is frequently a paid tier, or applied only to vessels you explicitly flag. A platform can accurately claim satellite integration while giving you terrestrial-only coverage on most of your fleet unless you pay more.

What happens in dense traffic? A satellite footprint can cover thousands of vessels transmitting simultaneously, and messages collide. Satellite AIS is therefore weakest precisely where traffic is heaviest, the opposite of the intuition most buyers bring to it.

There is also a counting problem worth naming. When a provider says it tracks 450,000 vessels, that figure usually counts any vessel seen at all during the period. A ship observed once a week counts the same as one reporting every two minutes. Ask which definition is being used before treating vessel counts as a comparison.

The practical test: ask for position frequency on one of your own vessels over a full week, rather than a coverage map. Coverage maps are marketing. Position intervals are evidence.

How to choose an AIS platform: the six things that actually differ

1. Coverage resilience, not coverage claims

Every provider claims global coverage, and in a broad sense, every provider has it. The difference is what happens where coverage is weakest: open ocean between satellite passes, congested waters where messages collide, and areas where a vessel would prefer not to be seen.

Ask what sources are combined, whether the platform can use anything beyond AIS, since independent position reporting over Inmarsat-C, Iridium, or onboard devices materially changes what happens when AIS stops, and whether you can see which source a given position came from. A platform that presents a smooth track without letting you inspect its provenance is asking for trust it has not earned.

2. Whether the workflow exists at all

This is the widest gap in the market and the least discussed. Some platforms are display tools: they show you where things are and leave the rest to you. Others are operational tools: they surface exceptions, route them to the right person, and keep a record of what was done.

The test is simple. Ask to see what happens between an alert firing and someone acting on it. If the answer involves opening a second system, the workflow does not exist.

3. Depth and usability of history

Most platforms retain history. Fewer make it usable. The questions that matter are how far back the archive goes, whether all of it is included or only recent months, how quickly a specific voyage can be reconstructed, whether the reconstruction can be exported in a form that survives a dispute, and whether historical positions carry the same source detail as live ones.

Depth varies more than buyers expect. Some providers hold a rolling twelve or twenty-four months; others hold several years or more. Ask two separate questions: how far the archive goes, and how much of it your plan actually includes. These are rarely the same number, ours included. For insurers, investigators and anyone facing a performance claim, this is often the single most valuable capability in the platform, and it is almost never demonstrated unless you ask.

4. The support model

Support quality is difficult to assess before you buy and expensive to discover afterwards. Ask who answers, what hours, and whether the person answering knows your fleet. Ask what happens when something is wrong with the data rather than the software. Ask for a reference customer with a fleet of a similar size and speak to them without the vendor present.

5. Commercial terms and honesty about them

Published pricing is a reasonable proxy for how a vendor treats customers. It is not the only acceptable model, since enterprise data agreements are legitimately complex, but a provider who will not indicate cost until late in the process is telling you something about the negotiation ahead.

Establish what happens when your fleet grows, whether additional users cost more, what history is included versus charged separately, and what the exit looks like: can you export your zones, watchlists and event history if you leave?

6. Whether the company will still be improving in three years

Roadmaps are marketing documents, so read them for direction rather than dates. The more useful signals are how the platform has changed in the last two years, whether customers influence what gets built, and whether the provider is independent or a small line item inside a much larger business with different priorities.

Where platforms barely differ

It is worth being equally clear about the criteria that consume evaluation time and change nothing.

• Raw vessel counts. Everyone draws on the same open broadcast, so headline counts cluster closely. Reception is where providers differ, not fleet size.
• Map aesthetics. Pleasant to look at, irrelevant within a fortnight of daily use.
• Long feature lists. Presence is not capability, and no procurement scoring model has ever detected the difference.
• Having an API. Almost everyone does. What matters is what is exposed through it and whether the documentation is real.

If what you want is a direct head-to-head on interface, coverage and cost between the better-known platforms, that is a different exercise from this one.

How to run a trial that tells you something

A trial is only useful if it stresses the things that will matter later. Five rules make the difference.

1. Use your own fleet and your own areas of interest. A demo dataset tells you nothing about your operation.
2. Run it for at least two weeks. One week shows you the interface; two shows you the alert volume, which is where most implementations quietly fail.
3. Give it to the people who would actually use it, not only to the person running the evaluation. A duty officer will find in an afternoon what a manager will not find in a month.
4. Test a bad day deliberately. Pick a vessel in a poor-coverage area, or a past incident, and see whether the platform can reconstruct it convincingly.
5. Raise a real support ticket during the trial and time the response. You are evaluating the company as much as the software.

Red flags

A few responses should slow an evaluation down. A refusal to discuss data sources in any detail. An inability to show provenance behind a position. A demo that cannot be repeated with your vessels. Reluctance to provide a reference customer of comparable size. Pricing that only appears after a procurement process has started. And any claim of complete, uninterrupted global coverage, which is not a thing that exists. A provider willing to say it will be willing to say other things.

Take this into the call

The questions below are drawn from the sections above. Each one is explained in context earlier in the article, which is worth reading before you use them, because the explanation is what stops a plausible-sounding non-answer from getting through.

Frequently asked questions

How do I choose an AIS platform for vessel movement monitoring?

Start from the decisions your team makes daily, rather than a feature list, then test six things: coverage resilience and source visibility, whether an alert leads to action inside the platform, how usable the history is, the support model, commercial terms, and whether the product is still being developed.

What are the leading maritime intelligence analytics platforms?

The market divides into three groups rather than a single league table. Public tracking sites optimised for breadth and casual use; maritime intelligence and analytics businesses aimed at data teams, risk and compliance; and operational platforms built around the daily workflow of fleet, port and security teams. Which group fits depends on whether you need a dataset, an analysis capability or a tool your duty officer will use every shift.

How can we ensure safety and compliance before signing a long-term vendor contract?

Run the trial on your own fleet, test a poor-coverage area deliberately, confirm the audit and export position early, and establish what happens to your zones, watchlists and event history if you leave. Ask for a reference customer of a similar size and speak to them without the vendor present.

Is satellite AIS the same across all providers?

No, though it is more similar than the marketing suggests. Several providers resell the same underlying constellations. What differs is revisit interval in your operating area, whether satellite coverage is included or a paid tier, whether it applies to your whole fleet, and how the provider handles message collision in dense traffic.

How long should a vessel tracking trial run?

At least two weeks, using your own fleet and areas. One week shows you the interface; two weeks show you the alert volume and whether the team will actually use it.

A note on how we would answer these

BigOceanData combines terrestrial and satellite AIS with independent cooperative tracking, keeps the source visible behind every position, and connects alerting, voyage replay and port activity in one workspace. The platform processes over 80 million position reports a day across the global fleet and 4,500 ports. The number that matters is how often a vessel is seen, not how many vessels are counted. Several years of movement history are available, with the depth included varying by plan. Prices are published, support is provided by a named team, and the platform has been developed continuously since 2016 on tracking work dating back to 1994.

Evaluate us on your own fleet. We will set up a trial using your vessels and your areas of interest, so you can judge the platform against your operation rather than a demo dataset.