Why a service technician is stopped at the gate
The gate makes its decision based on the verdict: training, qualifications, an active account and an authorization. For a technician from an external company, usually only the authorization is missing, because training and the account were handled during the first visit. If the authorization is issued for one day, every further day needs a new one, and this is only remembered at the gate.
From the security point of view this looks like a queue of guests waiting for manual checks. From the technician's point of view it is lost hours next to a machine that is standing still. Planning the visit in advance removes the cause.
Step 1: the host plans the visit in advance
Every visit has a host, meaning an internal employee of the plant. The host plans the technician's visit, because they know when the service should take place and how many days it needs.
Date range
A visit can be planned from today up to 377 days ahead, and no more than 34 days at once. For a service lasting a week or two this is more than enough, and a longer overhaul is split into several visits of up to 34 days each.
What the visit removes and what it does not
A planned visit is a one-day equivalent of an authorization, with no time limit, and in the gate verdict it removes only the authorization requirement. Training, qualifications and an active account still decide on entry. A technician whose safety training has expired will not get in despite the visit, so the host checks that training is valid before the visit.
Visit planning limits
Step 2: notifying the host at the first arrival
When the guest first arrives on the day of the visit, the dispatcher calls the host once, with no retries. The host is therefore not called at every entry of the technician, and security knows that someone responsible has been informed.
If the host has no phone number, the system sends them one email asking them to add the number, instead of staying silent. It is worth adding the numbers of all hosts before the first multi-day service.
Step 3: the service crew, meaning a group of guests of one host
A service job is rarely done by one person. A group of guests belonging to one host produces one combined call after 30 seconds of silence within a 3-minute window. Four technicians in one car, or in several cars driving together, do not generate four calls to the host.
Each crew member must be planned separately, because the visit concerns a person, not a vehicle. This is a detail that is often missed: the host plans one technician, and the other two find out about the stop at the gate.
Contingency plan: the technician arrived without a visit
If the only missing item is the authorization, security can set a visit for today for a person from an external company at the gate, and entry is recorded the same way as a scan. This is a solution for emergencies, not a daily method: the plant should state in its procedure who in security has this authority, and track such cases as a signal that hosts are not planning visits.
InnerWeb does not describe reading vehicle registration plates or controlling a barrier. The entry of the technician's car therefore depends on the client's access control system, and InnerWeb's role is the verdict and the register. A multi-day visit does not replace the decision of the vehicle access control vendor on how to open the barrier.
Checklist
Video
Frequently asked questions
Does a multi-day visit have to be planned every morning?
No. A visit is planned in advance for up to 34 days at once, so one entry covers the whole service.
Does a visit replace safety training?
No. It removes only the authorization requirement. Training, qualifications and an active account still decide on entry.
Who is responsible for the service technician on site?
The host, meaning the internal employee of the plant. The dispatcher calls them once, at the first entry of the guest on the day of the visit.
Plan service visits without stops
We will show how the host plans a multi-day visit and what security sees at the gate. Book a demo with the InnerWeb team.
Let's talk