Who these recommendations are for
The recommendations are addressed to the security manager of a fuel depot who prepares the gate procedure for drivers from external transport companies. They are most useful at the stage of preparing the procedure, before the first entry under a new scheme.
Each recommendation is based on how the system handles deliveries. We do not assume that the plant has one ready-made pattern. A plant with a delivery pre-arrival system can connect it to InnerWeb over SOAP, while a plant without such a system records deliveries by hand in a form.
Recommendations 1 to 3: delivery data at the gate
Recommendation 1: establish where the gate gets its data from. When the plant has a pre-arrival system, InnerWeb retrieves the delivery data from the access code of the pre-arrival and pre-fills the gate, dock and carrier form. The guard confirms the data instead of typing it from scratch, which shortens processing and reduces spelling errors.
Recommendation 2: plan for a missing carrier in the pre-arrival. When the pre-arrival data does not include a carrier, the delivery form substitutes a placeholder value so that the entry can still be registered. The procedure should state who fills in the carrier after the entry and when, so that the placeholder does not stay in the data permanently.
Recommendation 3: decide what to do with a completed transport. A transport with the completed status is deliberately treated as missing data. The pre-arrival system can return the last completed transport for many non-matching codes, and showing it would confuse the driver and raise a GDPR risk. The guard should know that the message "no transport" is not a fault.
Recommendations by procedure stage (number of recommendations)
Recommendations 4 and 5: route and locator
Recommendation 4: describe the standard route of a tanker driver. On large sites the route consists of several stages, and the system measures the time of each one. Without a route description it is hard to define what counts as a deviation. The description should cover the gate, the weighbridge, the loading or unloading point and the exit.
Recommendation 5: decide whether the driver gets a locator. The delivery route view isolates one active delivery and shows the locator's route from the entry, the stops longer than one minute and the pin of the declared destination. For the guard, this means being able to check whether the tanker stands where it should.
- hand out the locator at the gate and record the device in the delivery,
- check offline devices and those with a battery at or below 5 percent in the service tab,
- collect the locator at the exit so that it does not drop out of circulation.
Recommendations 6 and 7: recording events and reaction
Recommendation 6: use the record of reads. Every read of a pre-arrival access code is saved with its result, response time and operator. When carriers report that cards do not work, the security manager can confirm or refute it with numbers rather than argue from impressions.
Recommendation 7: define the reaction to a deviation. The stage timer raises an alarm by phone once a stage exceeds its standard time. The procedure should state who receives the alarm, whom it sends to the site and when the dispatcher is informed. An alarm without an assigned reaction turns into noise.
What not to assume
Do not assume that the locator replaces the guard's control. It provides information about the route and the stops, while the decision to admit and the reaction stay with a person. Also do not assume that every pre-arrival access code will return data: some will return "no transport", and this is intended behaviour.
For zones at risk of explosion, the choice of equipment requires separate arrangements consistent with the plant's zone classification. Details of this topic are covered on the pages about ATEX transmitters and the scope of the location system.
Video
Frequently asked questions
Is a pre-arrival integration required?
No. The plant can record deliveries in the form by hand. The SOAP integration with the pre-arrival system shortens processing but is not a condition for starting.
Why does the system not show a completed transport?
The pre-arrival system can return the last completed transport for many non-matching codes. Showing it could confuse the driver and expose the plant to a GDPR risk.
How do I confirm that the access cards do not work?
From the record of reads, which contains the result, the response time and the operator. Reports can be confirmed or refuted with figures.
What about a driver without a locator?
The entry is registered in the form. Stage measurement and route view require a locator, so the procedure should define when it is issued.
Prepare a tanker gate procedure
We will go through the seven recommendations together on your delivery scheme. Book a call or a demonstration.
Let's talk