📡 Terminal Data Integration
This guide explains how Dockflow integrates multiple data sources to deliver accurate, timely visibility into container movements and terminal operations.
Overview
Dockflow gathers terminal and shipment information from multiple sources, each with unique strengths. By combining these sources, the platform provides comprehensive tracking of key milestones such as vessel arrival, container discharge, and gate-out events.
Events like discharge and gate-out physically occur at the terminal. The difference lies in how Dockflow receives this data:
- Direct terminal integration → Data comes straight from the terminal system (faster)
- Via ocean carrier → The same data is relayed through the carrier's systems (may have processing delays)
Both paths deliver the same event information—the distinction is speed and directness of the data feed.
Container Event Lifecycle
A container goes through multiple events during its journey:
Empty Gate Out → Full Gate In → Load on Vessel → Vessel Departure → Vessel Arrival → Discharge → Full Gate Out → Empty Gate In
| Event | Description |
|---|---|
| Empty Gate Out | Empty container picked up from terminal or depot |
| Full Gate In | Loaded container enters terminal for export |
| Load on Vessel | Container loaded onto vessel |
| Vessel Departure | Vessel leaves port |
| Vessel Arrival | Vessel arrives at destination port |
| Discharge | Container unloaded from vessel |
| Full Gate Out | Loaded container leaves terminal for delivery |
| Empty Gate In | Empty container returned to terminal or depot |
Dockflow's direct terminal integrations currently focus on the import events (Vessel Arrival → Discharge → Full Gate Out). Export events and empty container movements are on the roadmap.
Data Sources
Dockflow gathers event data from multiple sources, each with unique strengths:
| Source | Coverage | Speed |
|---|---|---|
| 🛰️ Satellite | Vessel arrival & departure | Earliest |
| 🏭 Terminal | All events | Fastest |
| 🚢 Carrier | All events | Always available |
Terminal and Carrier provide the same event data—the difference is latency. Carrier data may have processing delays.
🚢 Ocean Carrier Data
Carrier data provides a structured view of vessel and container activities. Using client booking or container numbers, this source delivers events across both import and export flows.
Carrier data is typically reliable for documenting completed events but may lag behind other sources due to carrier-specific processing timelines.
🏭 Direct Terminal Integrations
Direct integrations with terminal systems provide granular, near-real-time updates. These integrations connect directly to terminal operating systems, bypassing carrier intermediaries:
| Event Type | Description |
|---|---|
| ETA | Accurate estimates of vessel arrival times at terminal berths |
| ATA (Actual Arrival) | Confirmation when vessels actually arrive |
| Discharge | Immediate confirmation when containers are unloaded |
| Full Gate Out | Tracking of loaded containers exiting terminal gates |
Direct terminal integrations provide the fastest updates for container-level events. Some integrations also provide vessel arrival confirmation. Coverage is limited to terminals where integrations are established.
🛰️ Satellite Tracking with Geofencing
Satellite tracking monitors vessel movements using geofencing technology. By mapping predefined polygons around global terminals, the system captures:
| Event Type | Description |
|---|---|
| Vessel Arrival | Identifies when a vessel enters a terminal's geofenced area |
| Vessel Departure | Tracks when a vessel exits the geofenced area |
Satellite data provides the earliest visibility into vessel movements—often before carrier or terminal systems report the event. Position data is also used to validate ETAs received from other sources—by knowing the vessel's current position and destination, Dockflow can evaluate whether an ETA is plausible.
However, satellite tracking cannot detect container-level events (discharge, gate-out) since these occur within the terminal.
Dockflow is developing capabilities to identify which specific terminal a vessel will use:
| Capability | Method | Status |
|---|---|---|
| Where did it arrive? | AIS geofencing detects which terminal the vessel entered | 🔄 In progress (wider support) |
| Where will it arrive? | Requires carrier or terminal integration data | 🔄 In progress (limited support) |
Actual terminal identification (after arrival) will have broader coverage since it relies on satellite tracking. Predicted terminal (before arrival) depends on external data sources.
Available Integrations
Integration Systems
Dockflow connects to various systems to retrieve terminal data. Some terminals are accessible through multiple systems.
Dockflow does not charge extra for enabling terminal integrations. However, some data providers may require a separate paid subscription on your end (e.g., MyTerminal, Portbase).
🇳🇱 Netherlands
| Terminal | System | Events | Status |
|---|---|---|---|
| All terminals | Satellite (AIS) | ETA, ATA, ATD | ✅ Active |
| All terminals | Carrier | All events | ✅ Active |
| ECT Euromax | MyTerminal | ETA, ATA, Discharge, Gate Out | ✅ Active |
| ECT Euromax | Portbase | ETA, Discharge, Gate Out | 🔄 In progress |
| Hutchison Delta II | MyTerminal | ETA, ATA, Discharge, Gate Out | ✅ Active |
| Hutchison Delta II | Portbase | ETA, Discharge, Gate Out | 🔄 In progress |
| APM Terminals MVII | Portbase | ETA, Discharge, Gate Out | 🔄 In progress |
| APM Terminals MVII | APM e-Tools | ETA, Discharge, Gate Out | 🔄 In progress |
| RWG | Portbase | ETA, Discharge, Gate Out | 🔄 In progress |
| RWG | RWGServices | ETA, Discharge, Gate Out | 🔄 In progress |
System Access:
- MyTerminal: Paid subscription, client credentials required
- Portbase: Portbase subscription required
- APM e-Tools / RWGServices: Free, client signup required
🇧🇪 Belgium
| Terminal | System | Events | Status |
|---|---|---|---|
| All terminals | Satellite (AIS) | ETA, ATA, ATD | ✅ Active |
| All terminals | Carrier | All events | ✅ Active |
| PSA Antwerp (869, 913) | PSA ePortal | ETA, Discharge, Gate Out | ✅ Active |
| PSA Antwerp (869, 913) | NxtPort | ETA, Cargo Opening | ✅ Active |
| DP World (1700) | DP World ePortal | ETA, Discharge, Gate Out | ✅ Active |
| DP World (1700) | NxtPort | ETA, Cargo Opening | ✅ Active |
| MPET (1742) | MPET Connect | ETA, ATA, Discharge, Gate Out | ✅ Active |
| MPET (1742) | NxtPort | ETA, Cargo Opening | ✅ Active |
| CSP Zeebrugge | CSP ePortal | ETA, Discharge, Gate Out | 🔄 In progress |
| CSP Zeebrugge | NxtPort | ETA, Cargo Opening | ✅ Active |
System Access:
- Terminal Portals (PSA, DP World, MPET, CSP): Free, client signup required
- NxtPort: No credentials required (vessel ETA + cargo opening)
Release & Customs Platforms
Beyond tracking events, the following platforms provide release status and customs clearance information. These answer "Can I pick up this container?" rather than "Where is this container?"
🇧🇪 Belgium
| Platform | What It Provides | Status |
|---|---|---|
| NxtPort Certified Pick Up (CPu) | Secure container release for Antwerp-Bruges. Replaces PIN codes with identity-based authorization. Tracks release rights from shipping agent → freight forwarder → transport operator. | 🔄 In progress |
| IRP (Inbound Release Platform) | Customs declarations, temporary storage status, release confirmations for EU imports | 🔄 In progress |
| T-Mining Secure Container Release | Electronic delivery orders (eDO), secure pickup authorization | 🔄 In progress |
🇳🇱 Netherlands
| Platform | What It Provides | Status |
|---|---|---|
| Portbase Secure Chain | Secure release rights sharing for Rotterdam. Becoming mandatory for imports from Latin America, Far East Asia, Africa, and Middle East. | 🔄 In progress |
| Portbase Cargo Controller | In addition to tracking, includes customs status and release information | 🔄 In progress |
- Tracking data tells you where the container is (e.g. discharge and gate-out events)
- Release data tells you if the container is cleared for pickup (customs release, commercial release, pickup authorization)
How Data Sources Work Together
Each data source complements the others, creating a layered approach to event tracking:
| Source | Strength | Limitation |
|---|---|---|
| Satellite | Earliest vessel detection | No container events |
| Direct Terminal | Fastest container events | Limited terminal coverage |
| Carrier | Comprehensive coverage | May have processing delays |
Example: Tracking a Vessel Arrival
- Satellite detects the vessel entering the port's geofenced area → earliest alert
- Terminal confirms berthing and provides ATA → operational detail
- Carrier validates the arrival as part of the shipment record → authoritative confirmation
By combining these inputs, Dockflow minimizes latency, enhances accuracy, and ensures redundancy in tracking critical events.
Key Takeaways
- Same events, different paths: Discharge and gate-out events originate at terminals—the difference is whether Dockflow receives data directly or via carriers
- Layered visibility: Multiple sources provide redundancy and the fastest possible updates
- Terminal integrations require setup: Direct integrations often require client credentials or subscriptions
Need help setting up a terminal integration? Contact [email protected].