No customer site is live yet. We are looking for our first site and will measure before and after. We would rather say that than invent a customer reference.
Not as a hosted solution today. DockScheduler is installed for each customer, either in their own data center or on their premises. Operation by Brendel is technically possible, but not promised. Only the free trials run on our servers, each with its own database, for demonstration purposes.
Price on request. There is no price list during the pilot phase.
No. DockScheduler runs independently. Integration is possible, but not required.
No. The portal runs in the browser. The driver receives a link via SMS and needs neither an account nor an app, but can add the page to the home screen.
The driver is recorded and can be scheduled. Any event that is not recorded will be missing from all subsequent reports.
What it is called in the interface is set per site in the master data. Dock, door or bay: the screens use that name.
Yes. Operating hours apply per site; slot length, buffers, and restrictions also apply per dock. A maximum number of bookings per day can be defined for each carrier.
Colors, fonts, and the logo are stored in a brand sheet, separate from the rest of the interface. A second customer gets a brand sheet, not a second interface.
Yes, via a dedicated interface. The reader reports the license plate number and receives a decision in response: admit, wait, or reject, each with a reason. Without a matching booking, the barrier stays closed; the vehicle is still recorded. The interface has not yet been tested against real hardware; the first integration will take place at a pilot site as a dedicated project, together with the hardware vendor.
No. Devices poll for commands instead of receiving them. Your system checks whether a command is pending and requires no inbound connection. An open command expires after two minutes: a barrier that wakes up and opens after a network outage is more dangerous than one that does nothing.
Each connected system receives its own key with a name indicating who is working with it. Read access is sufficient for synchronization; anyone who needs to book and cancel requires explicit permission. Yard devices have separate keys so that a third-party system cannot open a barrier.
The portal, registration, driver page, and messages to the driver are available in eleven languages: German, English, French, Swedish, Polish, Romanian, Lithuanian, Czech, Hungarian, Bulgarian, and Slovak. The selection follows long-distance haulage to Germany; French and Swedish were added with the first target markets. The carrier changes the portal language in the header and selects the language for the driver's SMS when booking. Cancellation reasons are translated as well, because a reason nobody can read does not prevent phone calls.
Yes, in German, English, French, and Swedish. Each user selects their language in the application header. The CSV export remains in German formatting so that Excel processes the numbers correctly.
We walk through the process on our test system with your docks, operating hours, and restrictions, plus status, roadmap, and the pilot offer.