That holds up while volume is low. Once it grows, friction hits four areas.
{{ aktivText }}
The wait time in this example would not be estimated in actual operations: it is the interval between checking in at the gate and arriving at the dock, two timestamps captured during routine work anyway.
Such as dairies and food manufacturers. A refrigerated trailer is offered only docks in the matching temperature zone; the weight ticket is attached as a document to the appointment.
Designed for one or more sites, a handful to a few dozen docks, and dozens to hundreds of appointments per day.
Not a warehouse management system and not a transport management system; here, yard means truck traffic from gate to exit, without trailer or parking-space management.
Two separate interfaces with dedicated keys. An ERP system queries slots and books; a yard device reports what it detects and requests instructions. A third-party system cannot open a barrier, and a camera cannot cancel a booking.
The camera decides nothing. It reports a license plate and receives a response: admit, wait, or reject, each with a reason in plain text. The decision is made as at the gate: the license plate identifies the booking.
License plate reader, barrier, display board, scale, and terminal can be connected via a dedicated interface. It has not yet been tested against real hardware; the first integration will happen at a pilot site as a dedicated project, together with the hardware vendor.
Fully built, it runs in our test environment across twelve months and nearly 23,000 appointments. We do not quote savings figures because no one has measured them in production yet.
No site is using DockScheduler in live operation yet. We are looking for the first site and will measure with you before and after.
We walk through the process on our test system with your docks, operating hours, and restrictions, plus status, roadmap, and the pilot offer.