Limenis Türkiye
Traffic Engine
We manage the traffic before it becomes your queue.
Hinterland traffic is part of the gate. The engine decides who comes now, who waits and who moves their slot.
What it does
- ETA for every booked truck from live traffic data: Google Maps, Yandex Maps, optionally HERE or TomTom.
- Instructions by gate capacity and queue: come now, go to the waiting area or move your slot.
- Data sharing with VMS signs on approach roads and the city traffic centre.
- Queue forecast and P90 waiting-time forecast.
Traffic Engine
Call by capacity.
Not by queue.
Weigh the vessel's ETA, the block and equipment plan, road load, park occupancy and each truck's expected arrival in the same decision loop.
The models that solve capacity constraints with mathematical optimisation have been developed.
6 places free in the yard. 4 trucks on the road.
The call budget does not only look at free places. It also reserves room for trucks on the way and prevents extra capacity use.
If the other job, permit and safety conditions also hold. Entry rate and time spacing are limited separately.
This simplified explanation is not the production algorithm or real field data.
What does the operator see?
Reason for the decision • data time • forecast confidence • constraints • model version • approval and rollback record
At a glance
| Group | Plan |
|---|---|
| Status | In product |
| Measured by | P90 waiting time, queue length on approach roads |
| Works with | Smart VBS: appointments and slots, Driver check-in: geofence and kiosk, Truck Call-Forward |
Next step
Make your port's flow
measurable.
For a pilot scope we need daily and peak trucks, number of gates, park capacity, transaction types and TOS version.