Five modules on one port call. Every one of them is a working part of this page.
Quayside is a berth plan, a call timeline, a document set, a message exchange and a reporting layer over the same record. Nothing below is a screenshot: the planner rules, the timeline, the checklist, the message log and the chart all run here.
Berth Planner
The board on the home page, with your berths, your crane pool and the tide station nearest your quay. Every move is checked against five rules before it is saved, and every save is versioned with the planner who made it.
The checker alongside is the same rule engine, run on one hypothetical call at Terminal Noordkade. Change the vessel and watch which rules fail.
- Rules
- Overlap, LOA, depth alongside, channel tide window, cranes
- Horizon
- 72 h board, 21 days schedule
- Snap
- 30 min, configurable to 15
- Audit
- Every move, planner and result
Vessel Timeline
One port call, from pilot on board to last line away, recorded as it happens. Terminal operations, the agent and the pilot station write to the same timeline; the times are stamped by whoever reported them, not typed in afterwards.
Drag the handle to read the state of MSC ELOISE at any minute of her call on 14 May 2026.
- Events
- 21 standard, plus terminal-defined
- Sources
- AIS, mooring gang tablet, TOS, agent
- Export
- Per call, per berth, per line, CSV or API
Port-Call Documents
The set a call cannot sail without: pre-arrival notification, dangerous goods manifest, waste declaration, crew and security details. Quayside knows which are due, who owes them and how long they have been late, and it will not let a call be marked ready while one is missing.
Click a state to cycle it. The completeness bar and the deadline follow.
- Sets
- EU MSW, IMO FAL, terminal-specific
- Chasing
- Automatic to the agent at T−24 h and T−6 h
- Retention
- 7 years, WORM storage
Data Exchange
Every message in and out of the terminal, in one log, mapped to the call it belongs to. EDIFACT in and out, AIS positions, port community notifications, and signed JSON webhooks for anything your own systems need to hear about.
This is the live tail of the Noordkade exchange, replayed at a tenth of real speed.
- Throughput
- 1.9 M messages a day, all terminals
- Delivery
- At-least-once, ordered per call, 30-day replay
- Failures
- Retried 8 times over 6 h, then paged
Reporting
Berth utilisation, idle hours per call, crane productivity, conflicts caught before the day of the call, message failure rate. Weekly to the operations manager, monthly to the board, and the same figures over the API for your own warehouse.
Berth utilisation at Terminal Noordkade, by month. Hover or focus a bar for the number.
- Standard reports
- 11
- Grain
- Per call, per berth, per shift, per line
- Delivery
- PDF, CSV, API, or straight to a BI warehouse