Where Does Dockflow Get Its Data?
Dockflow combines multiple independent data sources to give you the most accurate and timely view of your shipments. This page explains what those sources are, what each one is good at, and how they work together.
The Three Pillars
Every container milestone in Dockflow is backed by at least one - and often multiple - data sources:
| Source | What it tracks | Typical speed | Coverage |
|---|---|---|---|
| Satellite / AIS | Vessel position, arrival & departure | Earliest (minutes) | Global - every vessel |
| Direct Terminal | Container discharge, gate out, ETA | Fast (near real-time) | Terminals with active integration |
| Ocean Carrier | Full shipment lifecycle | Reliable but may lag (hours) | All carriers we support |
No single source is perfect. Carrier data is comprehensive but can lag. Terminal data is fast but only available where we have integrations. Satellite data gives the earliest vessel signal but cannot see inside a terminal. By combining all three, Dockflow maximizes both speed and accuracy.
Satellite / AIS Tracking
Dockflow monitors vessel movements worldwide using AIS (Automatic Identification System) data combined with geofencing - virtual boundaries drawn around ports and terminals.
What it provides:
- Vessel arrival detection (vessel enters port geofence)
- Vessel departure detection (vessel leaves port geofence)
- Real-time vessel position for ETA validation
Why it matters: Satellite tracking often detects a vessel arrival before the carrier or terminal reports it. It also serves as a cross-check: if a carrier says a vessel will arrive tomorrow, but satellite data shows it is still 3 days away, Dockflow can flag the discrepancy.
Limitation: Satellite data tracks the vessel, not individual containers. It cannot tell you when your container was discharged or when it left the terminal gate.
Direct Terminal Integrations
Where available, Dockflow connects directly to terminal operating systems. This bypasses the carrier entirely and provides container-level events as they happen.
What it provides:
- Vessel ETA at berth
- Actual vessel arrival (ATA)
- Container discharge confirmation
- Gate out (container leaves terminal)
- Cargo opening date (via NxtPort in Belgium)
Current terminal coverage:
| Region | Terminals |
|---|---|
| Belgium | PSA Antwerp, DP World Antwerp, MPET, CSP Zeebrugge (via NxtPort) |
| Netherlands | ECT Euromax, Hutchison Delta II, APM Terminals MVII, RWG |
For full details and setup instructions, see Terminal Data Integration and Data Sources Setup.
Limitation: Only available at terminals where integrations are established. For other terminals, Dockflow relies on carrier data and satellite tracking.
Ocean Carrier Data
Dockflow connects to 60+ ocean carriers and retrieves structured shipment data using your booking references or container numbers.
What it provides:
- Complete shipment lifecycle (booking, loading, departure, arrival, discharge, gate out)
- Vessel and voyage information
- ETA updates from the carrier
- Route and transhipment details
Reliability: Carrier data is the most comprehensive source - it covers every event from origin to destination. However, it can lag behind reality because carriers update their systems at their own pace (typically every 4-8 hours, sometimes longer).
For the full list of supported carriers, see Supported Carriers.
How They Work Together
Here is a real-world example of how the three sources complement each other when a vessel arrives at Antwerp:
- Satellite detects the vessel entering the port geofence - you get the earliest arrival signal
- Terminal (e.g. PSA) confirms berthing and provides the exact ATA - operational detail
- Carrier updates the arrival milestone in their system - authoritative record
For container-level events:
- Terminal reports discharge within minutes of it happening
- Carrier confirms the same event hours later
- Dockflow uses the fastest available source and cross-references with the others
When sources disagree, Dockflow applies priority logic: direct terminal data and satellite observations take precedence over carrier-reported estimates. For completed events (actuals), the first confirmed source wins. For predictions (ETAs), Dockflow evaluates plausibility using vessel position data.
ETA Accuracy
ETAs in Dockflow come from multiple sources and are continuously refined:
| ETA Source | When it is used |
|---|---|
| Carrier ETA | Default - the carrier's own estimate based on their schedule |
| Vessel schedule | Cross-referenced with published vessel rotation schedules |
| AIS / Satellite | Used to validate or override carrier ETAs based on actual vessel position and speed |
| Terminal ETA | Where available, terminals provide their own berth window estimates |
What can cause ETA discrepancies?
- Port congestion or strikes (e.g. pilot strikes) can delay or accelerate actual arrivals vs. scheduled ETAs
- Carrier schedule changes not immediately reflected in all systems
- Vessels arriving early when conditions are favorable (weather, reduced port calls)
- Blank sailings or port skips changing the route mid-voyage
Dockflow's Data Quality metrics let you monitor the freshness and accuracy of your data in real time.
Data Quality & Freshness
Dockflow tracks data quality through measurable metrics available in your Console:
| Metric | What it measures | Target |
|---|---|---|
| Freshness | Hours since last carrier data update | < 6 hours |
| TTFF (Time to First Fix) | Hours from container added to first data received | < 8 hours |
| Confirmation Delay | Time between event happening and Dockflow confirming it | Coming soon |
For details, see Data Quality Dashboard.
Summary
| Question | Answer |
|---|---|
| Where does vessel position data come from? | AIS / Satellite tracking (global coverage) |
| Where do container events come from? | Direct terminal integrations + ocean carrier data |
| How fast is the data? | Terminal: near real-time. Satellite: minutes. Carrier: hours. |
| How many carriers are supported? | 60+ ocean carriers (full list) |
| Which terminals have direct integration? | PSA, DP World, MPET, ECT, Hutchison, APM, RWG (details) |
| What if sources disagree? | Dockflow applies priority logic favoring direct observations over estimates |
| Can I monitor data quality? | Yes - via the Data Quality Dashboard |
Learn More
- Terminal Data Integration - Technical details on how terminal integrations work
- Data Sources Setup - How to connect your terminal accounts
- Supported Carriers - Full carrier list
- Data Quality Dashboard - Monitor freshness and accuracy
- ETA Definitions - What ETS, ETA, ATS, ATA mean
Questions? Contact [email protected].