Block 1: appointment data
If the plant has a delivery appointment system, it can be connected to InnerWeb via SOAP. After the appointment card code is scanned, the system fetches the delivery data and pre-fills the gate, dock and carrier form. Before starting, the coordinator checks that the connection returns data for several test codes, not only that it works technically.
Two behaviours of the system must also be known. When the data contains no carrier, the form inserts a substitute value so that entry can be registered. A transport with a completed status is deliberately treated as no data, because the appointment system can return the last completed transport for many non-matching codes, and showing it would mean confusing the driver.
Block 2: driver locators
The service tab for driver locators is read-only. Devices that are offline or have a battery down to 5 percent receive the recommendation 'Recharge and switch on'. Before starting, the coordinator reviews the tab and recharges the devices, because a driver with a non-working locator is invisible on the map.
It is also worth checking how many locators are in circulation compared with the number of planned deliveries. A spare stock allows the units that came back with a low battery to be swapped out.
Split of checklist points by block
Block 3: delivery route and stages
The delivery route view isolates one active delivery and shows the locator route from the entry, stops longer than one minute and the pin of the declared destination. Before starting, the coordinator makes a test drive with a locator and checks whether the route is readable on all road sections.
For delivery stages, for example the gate, the weighbridge and the warehouse, a standard time is set. The stage time alarm rings the phone when a stage exceeds that time. A time that is too short generates false alarms, and one that is too long misses problems, so the values are chosen after several days of measurement.
Block 4: recording and reporting
Every reading of an appointment card code is saved with its result, response time and operator. In this way recurring reports of non-working cards can be confirmed or refuted with numbers. Before starting, the coordinator checks that the recording works and who has access to the report.
The full delivery run, that is routes and times per warehouse, goes into the reports. After the first week it is worth reviewing them and deciding which stages need a correction of thresholds or a conversation with the carrier.
What the checklist does not replace
The list covers data and devices, not regulations. Procedures for entering the depot, requirements for drivers and Ex zones are set by the plant in its own documents. The system provides visibility and recording, but does not replace the gate instructions or the driver training.
Checklist
Video
Frequently asked questions
What to do when the appointment has no carrier?
The delivery form inserts a substitute value, so the entry can be registered; the data is completed later.
Why does the system not show data for a code with a completed transport?
A completed transport is treated as no data, so the driver is not confused with the previous delivery.
How to check which locators need charging?
In the service tab, which shows devices that are offline or have a battery down to 5 percent.
How to set the stage times?
From several days of measurements in the reports, followed by a correction of the stage time alarm threshold.
Start the gate with a ready checklist
Book a call with InnerWeb and match the checklist to the appointments, the locators and the delivery stages at your depot.
Let's talk