Starting point: the JIT window and one mistake at the gate
A parts plant receives deliveries in step with its assembly line. The component has to arrive within a time window, and a delay of a dozen or so minutes can stop the workstation that is waiting for it. That is why every minute lost at the gate counts twice: once as security time and a second time as a risk to production.
In this scenario we assume a plant with a dozen or so unloading docks and several warehouses. A foreign driver reaches the gate, shows the delivery card and the transport document. The guard copies the registration number and the carrier name, then picks the dock from memory or from a note at the post. At the peak of the shift this manual work ends in a mistake: a truck carrying parts for warehouse A drives to the dock of warehouse B.
Why the wrong dock costs more than a detour
A wrong dock is more than a few hundred metres of driving across the yard. The driver has to turn back, often manoeuvring among other vehicles, and on the way blocks the route of forklifts. The staff at warehouse A see that the delivery has not arrived and start asking security, so the number of phone calls grows at the worst possible moment.
The second cost is informational. When a delivery ends up at a different dock than planned, the warehouse system and the appointment system drift apart. Someone then has to explain by hand why the delivery was received late, and that takes the time of the planner and the shift manager.
- a driver who does not know the site loses orientation at the first junction on the yard
- security types data from the card and the documents, so every character is a chance for a typo
- the warehouse waiting for the delivery has no signal that the truck is heading the wrong way
- the planner learns about the delay only from the shift report
Time to handle one delivery at the gate
Scenario with the delivery card code, step by step
In the InnerWeb concept, security types or scans the code from the delivery card. The system pulls the data of the planned delivery from the client's appointment system and pre-fills the form: the gate, the dock or warehouse, and the carrier. The query to the appointment system is sent once, using the canonical five-character code, and codes stored with leading zeros in another form are reduced to one format, so the same delivery does not come back as two different queries.
The type of operation decides the label: unloading or loading. The service point name is matched against the warehouse codes in the dictionary of unloading docks, which the plant maintains in the panel. The guard sees a completed form, checks it with the driver and confirms it in one move instead of typing everything from scratch.
What about a driver who does not know the yard
For a driver with a BLE locator, the plant can turn on voice messages at junctions in one of 10 languages. The administrator sets, in an editable matrix, what to say at which junction for which warehouse. This is not live navigation, only a message matched to the point where the driver currently is. The position comes from averaging the signals of many transmitters on the map, so it works without GPS.
What if the code returns no delivery
The appointment system may be external and can return the last completed transport for codes it does not recognise. If such a response filled the form, a stranger driver and someone else's registration numbers would appear at the gate, which is a GDPR risk. That is why a delivery marked as completed in the appointment system is treated as no data: security fills in the form by hand and records the reason.
Effect: reception time in an illustrative calculation
Assume for illustration that the plant receives 60 deliveries a day and that typing the delivery data by hand at the gate takes 4 minutes on average. That is 240 minutes, or 4 hours of security work a day spent only on retyping. When the form is filled from the appointment card and the guard only verifies the data, this time can drop to about one minute per delivery. This is an assumption to be replaced with a measurement at the plant's reader, not a result from a deployment.
The larger value lies beyond the stopwatch. The driver immediately gets the indication of the point, the warehouse sees the delivery assigned to its dock, and every code read goes to telemetry: the code entered, the result, the transport status, the response time and the operator. A failure to write telemetry does not stop the work of security, so the gate keeps working even if the diagnostic trace temporarily fails to save.
What to prepare before starting such a scenario
The prerequisites are access to the client's appointment system and a completed dictionary of docks and carriers. This dictionary is not loaded by migrations: the system image stays generic, and the plant's data is entered in the panel, without changes to the code. In this way the same system can run in the next plants of the group.
For correct location of the driver on the yard, transmitters are needed: on the site roads roughly every 100 m, and inside buildings one every 100 to 200 m2. Only then do the delivery route trace and the voice messages make sense. The whole supplements the existing systems of the plant and does not replace them.
Delivery entry time at the gate per day
| Parameter | Value |
|---|---|
| Deliveries per day | 60 deliveries |
| Manual entry | 4 min per delivery |
| Verification of the form from the code | 1 min per delivery |
Result: 240 min by hand versus 60 min with a pre-filled form: a difference of about 3 hours of security work a day.
Note: Illustrative calculation based on example assumptions; to be replaced with a measurement at the plant's reader.
Video
Frequently asked questions
Does the system direct the truck to the dock on its own?
No. The system fills in the form and indicates the dock from the appointment data, and the driver optionally gets a voice message at a junction. It is a message from a matrix set by the administrator, not live navigation.
What if the appointment card code does not exist in the system?
The form stays without appointment data, and security fills it in by hand. A delivery marked as completed in the appointment system is deliberately treated as no data.
Do we have to change the system code for our plant?
No. The dictionaries of docks and carriers are filled in the panel, and the system image stays the same for all plants.
Does driver location require GPS?
No. The position is averaged from the signals of many BLE transmitters on the plant map.
Sources
Let us check deliveries in your plant
Book a talk about the gate and the dock in a JIT rhythm. We will show how the appointment card code fills in the form using data from a plant like yours.
Let's talk