The landside layer on top of your Octopi
Your Octopi runs the terminal. DMSLOG runs the landside around it — appointments, gate automation, billing and connectors — so the gate stops queuing blind and nobody re-keys anything.
Octopi — the cloud-based TOS for small and mixed-cargo terminals — keeps your yard and moves in order. DMSLOG bolts the landside layer on top, read-only to start. No rip-and-replace.
DMSLOG speaks the systems & data your terminal already runs
One documented API, plus EDI, EIR and FTP, reads from Octopi and feeds the ERP, data sources and planning tools already on your desk.
Your Octopi stays in place
DMSLOG is not a competing TOS. Octopi keeps its gate and yard authority — we bolt on the landside layer it is missing: appointments, gate automation, billing and connectors.
Vehicle Booking System
4–5× throughput per lane.
Gate automation & OCR · Virtual Kiosk
99.7% OCR accuracy.
Billing & Web Customer Portal
DSO −15 to −25 days.
EDI & API connectors
0 re-keying.
Bolt on the bricks you need — each one plugs into Octopi on its own
Post-payment appointments, booked to a real slot
The engine at scale
Book or let the carrier book
Trucks arrive on a slot instead of a queue, so the gate runs 4–5× more moves per lane — without touching Octopi’s gate authority.
A 5-second gate cycle, read automatically
Read, don’t type
Validated back into Octopi
The Virtual Kiosk and OCR turn the gate into a 5-second cycle at 99.7% read accuracy, with the events landing in Octopi as they happen.
Self-service storage-tariff billing
Amazon-like billing
ERP-agnostic
A web portal lets every landside customer see and settle their storage tariff, cutting DSO by 15 to 25 days across the board.
COPARN, CODECO, COARRI, BAPLIE & REST
One canonical model
No double entry
DMSLOG reads Octopi’s API and EDI feeds — COPARN, CODECO, COARRI, BAPLIE and REST — and projects them into one canonical model the landside apps all speak.
Why terminals bolt DMSLOG onto Octopi
Plug in, don’t rip out
One canonical model
Measurable throughput
Billing that closes faster
Zero re-keying
Start with one brick
Move the box and report its carbon in the same flow
Every gate event and move that flows through Octopi is already a data point. DMSLOG turns that same event stream into the CO₂ of your port moves — scope-3 figures you can report, not a spreadsheet guess.
Built to sit on top of the TOS you already run
Mechanics, not promises — the figures come from how the landside layer works, not from any one customer.
OCR read accuracy at the gate
Throughput per gate lane
EDI standards spoken (COPARN · CODECO · COARRI · BAPLIE)
Re-keying between Octopi and the landside
What the landside layer adds
A layer on top of the TOS you keep — read-only to start, writing back only on your terms.
Read-only to start
One canonical model
Write back on your terms
Octopi stays source of truth
How it plugs into Octopi
API and EDI in, canonical model in the middle, events back to Octopi. The TOS stays the single source of truth; nobody re-keys anything.
1. Connect
2. Project
3. Run the landside
4. Write back
We built DMSLOG to sit on top of the TOS you already run. Your Octopi keeps its gate and yard authority — we add the landside layer around it, appointments, gate automation, billing and connectors, with nobody re-keying anything.
Questions, answered
No. DMSLOG is not a competing TOS. Octopi keeps its gate and yard authority; we bolt on the landside layer around it — appointments, gate automation, billing and connectors.
Through API and EDI. COPARN, CODECO, COARRI and BAPLIE feeds, plus REST, 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 Octopi.
Yes. DMSLOG reads Octopi’s feeds first and runs the landside on top; write-back to the TOS is switched on only when you are ready.
Yes. Confirmed appointments and gate events flow back, so Octopi remains the single source of truth for the yard and the gate.
Yes. Take the Vehicle Booking System first, then add gate & OCR, billing and connectors when you are ready — each brick plugs into Octopi on its own.
Tell us which TOS you run
A few words about the TOS you run and your peak hours, and we set up a call (Zoom, Teams or Meet) to show the landside layer running on your own flow — no rip-and-replace.
Works with the systems you already run
Navis N4 · Tideworks · TotalSoft · CATOS · RBS