InnerWeb
Skip to main content

Vehicle access to the plant: in what order to roll out control

A plant director has three candidates for the first stage of vehicle control: guests, deliveries with a prior notice and driver location tags. We propose an order based on what each stage requires from the plant, and we point out the pitfalls that lengthen the rollout.

4
stages of vehicle control rollout
Source: rollout plan on the page
100 m
indicative spacing of transmitters on plant roads
Source: company data

Three stages and their dependencies

Vehicle control in InnerWeb is made of building blocks that are rolled out independently, but in a sensible order. The first block is guests and the scan at the gate, the second is the deliveries module with a prior notice, the third is driver location tags with navigation in the yard. The fourth, optional, is integration with the client's access control system.

The deliveries and prior notice module manages vehicles entering the plant: choice of gate, dock or warehouse, the driver and the completion of the delivery. Driver location tags use the same module, because the driver receives the device at the gate. That is why the location tag stage only makes sense once deliveries are already being registered.

Stage 1: guests and the scan at the gate

We start with guests, because this stage has the fewest dependencies. Scanning the QR code on a badge or the card number is the control itself, and every scan records a gate entry. In the first stage the plant configures the gate, the guard panel and planned visits, and the duty officers learn to read the system's verdict.

Pitfall: skipping the decision on who the host of a guest is. Without this decision the dispatcher has nobody to call at the first entry. We recommend appointing the hosts before go-live and completing their phone numbers.

Yearly time of manual entries in a paper register

Yearly time of manual entries in a paper registerBar chart: at 20 vehicles a day it is 250 hours a year, at 40 vehicles 500 hours, at 60 vehicles 750 hours.0200400600800h20 vehicles a day: 250 h250 h20 vehicles a day40 vehicles a day: 500 h500 h40 vehicles a day60 vehicles a day: 750 h750 h60 vehicles a day
Source: Example calculation: 3 minutes of entry per vehicle and 250 working days a year as assumptions

Stage 2: deliveries with a prior notice

After the card of the prior notice is scanned, the system fetches the data of the planned delivery from the client's prior notice system over SOAP and pre-fills the form. Integration with another prior notice system requires implementation work, so this stage should start with the question of which prior notice system the plant has and whether it provides an interface.

A delivery whose transport has already been completed in the prior notice system is deliberately treated as missing data, because an external system may return the last completed transport for unknown codes, which would risk substituting a driver who is not the right one. For the implementation team this is an important point: missing data is not an error, it is a safeguard. Every lookup by code goes into telemetry, so a report of a card that does not work can be confirmed or disproved with numbers.

Stage 3: driver location tags

The driver receives a BLE location tag at the gate, and the pool is limited to the gate's transmitters. The position comes from the signals of several transmitters averaged on the map, without GPS, and plant roads are covered with transmitters roughly every 100 m. This stage therefore requires physical placement of transmitters in the yard, which is a decision about the scope of installation.

Pitfall: launching the tags without the service tab. Devices that are offline or have a battery at or below 5 percent must be visible to security, otherwise the pool quickly loses credibility. It is worth planning the first review of the service list already on the day of go-live.

Stage 4: card swipes from the access control system

The system receives card swipe events from the client's access control system (webhook) and links them with qualifications, permits, attendance and working time recording. InnerWeb does not sell readers or cards and does not read licence plates, so this stage requires cooperation with the supplier of the existing access control system.

We recommend leaving it to the end, because it requires agreements with IT and the access control supplier, while the first three stages deliver value without it. The details of the division of responsibility are described on the page about licence plates and the barrier.

Indicative schedule

The order is not rigid, but the direction is clear: from the smallest dependencies to the largest. When estimating the workload the director may assume that each stage needs to be assessed separately, because it depends on the prior notice system, the number of gates and the layout of the yard. Pricing is individual, and the schedule is agreed once the number of gates and vehicles per day is known.

Video

Frequently asked questions

Where should we start if the plant has both guests and deliveries?

With guests and the scan at the gate. This stage has the fewest dependencies, and the duty officers learn a verdict that later serves the other processes too.

Does the prior notice integration work with every system?

The system fetches data from the client's prior notice system over SOAP. Integration with another prior notice system requires implementation work.

Do driver location tags require GPS?

No. The position comes from the signals of several BLE transmitters averaged on the map, and the transmitters are placed roughly every 100 m on plant roads.

Let us plan the stages for your plant

At the meeting we will agree the number of gates, the vehicles per day and the prior notice system, and then propose the order of the stages.

Let's talk