The landside layer on top of your Tideworks
Your Tideworks runs the terminal. DMSLOG runs the landside around it — appointments, gate automation, billing and connectors, bolted onto the TOS you already run.
Tideworks — Mainsail Vanguard, Spinnaker and Traffic Control — operates container and mixed-cargo terminals across the Americas and beyond. DMSLOG bolts onto it: no rip-and-replace.
DMSLOG plugs into the TOS you already run
One documented API, plus EDI and the COPARN / CODECO / COARRI / BAPLIE feeds, bolts the landside layer onto the terminal operating system on your desk — Tideworks first, and the others too.
Your Tideworks stays in place
DMSLOG is not a rip-and-replace. Tideworks keeps its gate and yard authority — we bolt on the landside layer it is missing: appointments, gate automation, billing and connectors.
Vehicle Booking System
Gate + OCR · Virtual Kiosk
Billing & Web Customer Portal
EDI & API connectors
Four bolt-ons, each one works on its own and plugs into Tideworks
See the window, book the slot
A million a year
Post-payment, no blind queue
Drivers book a slot that Tideworks confirms as the single source of truth, so the gate stops queuing blind — 4–5× throughput per lane.
Read the gate in 5 seconds
Plates & containers
Validated into Tideworks
A 5-second gate cycle with 99.7% OCR accuracy — the virtual kiosk handles the driver, Tideworks keeps the gate authority.
Every landside fee in one place
Self-service, ERP-agnostic
Reconciled across borders
Amazon-like self-service billing on the landside — storage and gate fees shown per container, DSO cut by 15 to 25 days.
One canonical model, no re-keying
COPARN / CODECO / COARRI / BAPLIE
REST both ways
COPARN, CODECO, COARRI, BAPLIE and REST land in one canonical model, so the landside apps speak one language whatever your TOS — zero re-keying.
Why terminals bolt DMSLOG onto Tideworks
Keep your TOS
One canonical model
A gate that stops queuing blind
Read the gate in 5 seconds
Bill the landside yourself
Start with one bolt-on
Move the cargo and report its carbon in the same flow
Every gate move Tideworks records is already a data point. The landside layer turns that same event stream into the CO₂ of your terminal — scope-3 figures you can report, not a spreadsheet guess.
What the landside layer adds
Mechanics, not a commitment — figures are typical ranges that come from how the landside layer works, not from any one terminal.
throughput per gate lane
OCR read accuracy at the gate
monthly billing & closing effort
re-keying between apps
What stays true whatever your TOS
Mechanics, not promises — this is how the bolt-on behaves on top of Tideworks, by design.
1 source of truth
1 canonical model
0 rip-and-replace
0 re-keying
How it plugs into Tideworks
1. Connect
2. Project
3. Run the landside
4. Write back
We don’t replace Tideworks — we bolt the landside layer onto it. The TOS keeps the gate and the yard; the terminal gets appointments, OCR, billing and connectors on top, with nobody re-keying a thing.
Questions, answered
No. DMSLOG is not a competing TOS. Tideworks keeps its gate and yard authority; we bolt on the landside layer around it.
Through API and EDI. COPARN, CODECO, COARRI and BAPLIE feeds are projected into one canonical model — no rip-and-replace.
Never. Data flows both ways automatically, so the gate and yard stay in sync with Tideworks.
VBS, gate & OCR, billing & the Web Customer Portal, and EDI / API connectors — each works on its own, so you can start with one.
Yes. DMSLOG bolts onto the TOS you already run — see Navis N4, Octopi, TotalSoft / CATOS and RBS.
Talk to us
Tell us which Tideworks products you run and your peak hours. We’ll show the landside layer running on your own flow — no rip-and-replace.
Works with the systems you already run
Navis N4 · Octopi · TotalSoft · CATOS · RBS