What the delivery module does at the gate
The delivery module accepts the driver card code, retrieves the planned delivery from the plant's booking system over the SOAP protocol and pre-fills the form: the gate, the ramp and the carrier company. The gate operator does not retype data, but only confirms what the booking system already knows.
The integration is one-directional in terms of source data: the booking system remains the owner of the delivery plan, and the gate reads it. This simplifies responsibility, but it means the quality of data at the gate depends on the quality of data in the booking system.
Order of implementation
The order of work matters, because earlier stages provide test data for the next ones.
- Stage 1: agreeing the interface. The logistics IT team provides the description of the booking SOAP service, access data for the test environment and the list of fields: gate, ramp, carrier company, transport status.
- Stage 2: reading a delivery by card code in the test environment. Check that for a known code the form is filled in correctly.
- Stage 3: edge cases. Unknown code, completed transport, no transport, no response from the service.
- Stage 4: the pool of locators assigned to the gate, and closing per locator.
- Stage 5: a service tab for devices that are offline or have a low battery.
- Stage 6: a trial at the gate with an operator and test drivers, then go-live.
Stages of the booking integration
Edge cases
Most work is required in situations where the booking returns something that is not a simple delivery.
Transport with a completed status
A transport with a completed status is deliberately treated as no data. The reason is practical: the booking system can return one shared last transport for many different unknown codes, which could indicate a stranger driver as authorised to enter. The logistics IT team should know this, because a driver whose transport was completed will see no delivery at the gate and will need a new booking.
No transport for a code
A code for which the booking returns no transport gives a form without pre-filled data. The gate operator decides whether the delivery is planned outside the booking or whether the driver is to be sent away. The rule should be written down, not depend on the operator.
No response from the booking service
When the booking service is unavailable, the gate should not block traffic without reason. Agree with logistics an emergency mode: manual completion of the form and adding the delivery to the booking after the service is restored. Record a response time limit for the service, so the operator does not wait indefinitely.
Locators and device service
A delivery with a driver card code also has a pool of locators assigned to the gate. The closing of a delivery is per locator, so a driver returning one of several devices does not close the others. For the logistics IT team this means it must agree how many locators belong to a gate and who is responsible for returns.
The service tab marks devices that are offline or have a battery at 5% or below as requiring charging. It is worth agreeing on the plant a rhythm for checking this tab, for example at the start of each shift, and a charging place close to the gate.
Implementation pitfalls
The most common pitfall is testing only on codes for which the booking has a correct delivery. Without trials on unknown and completed codes, the cases that most often appear in production remain invisible. The second pitfall is the lack of an interface owner on the logistics side: when the booking service changes version, the gate stops reading deliveries and nobody knows who should fix it. The third is unclear responsibility for locators at the gate.
Video
Frequently asked questions
Does the gate change data in the booking system?
No. The delivery module reads the delivery plan from the booking and pre-fills the form. The booking system remains the owner of the plan.
Why is a completed transport treated as no data?
The booking system can return one shared last transport for many unknown codes. Treating it as no data protects against indicating a stranger driver.
What does the service tab show?
Locators that are offline or have a battery at 5% or below, which require charging.
Integrating the booking with the gate?
We will go through the interface, the edge cases and the pool of locators with the logistics IT team, before the gate starts reading deliveries.
Let's talk