InnerWeb
Skip to main content

Technician visit at a chemical plant: from invitation to the scan at the gate

An external technician is due on site on the first day of a plant shutdown, and the maintenance manager does not want to check paperwork at the gate at 6 a.m. Below is an implementation scenario for a chemical plant: who issues the invitation, what the technician receives, how the gate works and what proof remains in the entry log.

4
conditions of the gate verdict
Source: card
200 min
guard time saved with 40 people
Source: sample calculation

Starting point: a shutdown and one technician

This scenario describes a concept for a mid-sized chemical plant preparing an installation shutdown. It is not a report from a specific deployment, but a model based on system functions: visit planning, the external companies module, the security guard panel and a QR token on the badge.

The maintenance manager orders a pump service from an external supplier. The technician comes once, for one day, but works on the installation, so they cannot enter simply because someone greeted them at the gate. The plant wants to know in advance who is coming, from which company, to whom and on what terms, and does not want a conversation at the gate that takes the guard several minutes.

Who is responsible on the plant side

The scenario involves four roles: the maintenance manager as the visit host, the guard at the gate, the health and safety specialist responsible for induction training, and the administrator who maintains the data of the external company. Each of them sees a different part of the same process, and none of them has to copy data into a separate spreadsheet.

Step 1: invitation and company data in one place

The external companies module keeps data on the company, its employees and guests in one place. The host adds the service company, names the person who will come and plans the visit in advance. The system supports planned visits, so the invitation does not have to be created on the day of arrival.

A planned visit serves at the gate as a one-day permit without a time slot. It removes only the requirement for a work permit from the verdict. Training, qualifications and an active account still decide whether entry is allowed. This rule matters in chemicals: the visit confirms that someone is expected, but it does not replace safety requirements.

  • The host enters the company and the technician, selects the visit day and the purpose.
  • The technician receives an invitation with a link to register by phone and to the induction training.
  • The administrator of company data sees who has completed registration and who has not.

Time to process 40 people at the gate on the first day of the shutdown

Time to process 40 people at the gate on the first day of the shutdownChart compares 240 minutes of manual verification with 40 minutes of QR token scanning for 40 people.050100150200250minManual verification: Total time: 240 min240 minManual verificationQR token scan: Total time: 40 min40 minQR token scan
Source: Sample calculation: 6 min and 1 min per person, 40 people

Step 2: badge with a QR token

The badge carries a QR token read at the gate. The label is printed from the guard panel, and the code contains no personal data: it is a long, unguessable string that the system assigns to a person. For an outsider who finds the label in the car park, the code says nothing.

For a chemical plant this has a practical meaning. The badge can be prepared before the technician arrives or issued at the registration point, and at the gate it is enough to hold the code to the scanner. The scanner works like a keyboard, so the guard does not have to learn a new device, and the code reaches the system in a fraction of a second.

Step 3: the scan and a verdict based on four conditions

The gate verdict rests on four conditions checked at the scan. They are: a complete set of valid trainings, no missing qualifications for the work in progress, a permit or a planned visit for today, and an active account for the person. All four must be met at the same time for the gate to show approval.

The guard panel is used to operate the gate and verify the people entering the site. The guard sees the photo, the company, the list of required trainings and the reason for refusal, if there is one. The guard does not decide from memory or from a conversation, only from one consistent verdict. If the technician has no training, the gate shows it already at the gate, not on the installation site.

A refusal is also kept in the system

An entry attempt ended with a refusal is saved as a separate event. For the chief of security it is proof that the check worked, and for the health and safety specialist it is a signal that the company needs its training completed before the next visit.

Step 4: the entry log as evidence

Entry and exit of a person are saved as events that form the entry log. In the shutdown scenario the log serves three purposes: it shows who is on site at a given moment, it is material for a plant audit, and it feeds the evacuation list if an alarm is raised during the visit.

This means a technician who entered at 6:10 and did not scan the exit does not disappear from the records. The entry stays open and, once the time on site exceeds the threshold, it goes to verification. We describe the mechanism for closing forgotten entries in a separate material on evacuation.

Sample calculation: time at the gate

The figures below are a sample calculation, not a measurement from a specific plant. It is assumed that a manual check of one person at the gate takes about 6 minutes: checking documents, calling the host, writing in a logbook. With a token scan we assume about 1 minute per person. If 40 people from external companies enter on the first day of the shutdown, the difference is 200 minutes of guard time, which is more than three hours.

The main point is not only the shorter queue. The essential change is moving the verification from the gate to the day before: gaps in training show up at the invitation stage, not at six in the morning.

Conclusions for a chemical plant

The scenario shows that a technician visit can be described as a sequence of four events: invitation, registration, scan, entry in the log. Each of them is evidence and each can be checked afterwards. A plant that wants to run such a flow should start with one gate and one service company, and only then extend it to more contractors.

It is also worth agreeing who owns the data of external companies. Without this decision the list of contractor employees quickly goes stale, and the gate refuses people who are in fact authorized.

  • Start with one gate and one service company.
  • Agree who owns the data of external companies.
  • Measure the time at the gate before and after the implementation.
  • Use refusals as feedback for health and safety.
Example calculation

Gate processing time on the first day of the shutdown

Assumptions
ParameterValue
People from external companies40 people
Manual verification6 min/person
QR token scan1 min/person

Result: 240 min with manual verification versus 40 min with scanning, a difference of 200 min

Note: Sample calculation based on the assumptions above; actual time depends on the number of gates and the plant's organization.

Video

Frequently asked questions

Is a planned visit enough to let the technician in?

No. The visit replaces only the permit requirement for that day. Training, qualifications and an active account still feed into the gate verdict.

Does the QR token contain personal data?

No, it is an unguessable string assigned to a person in the system. The data is held by the system, not in the code.

What happens when the technician has no training?

The gate shows a refusal and the reason, and the attempt is saved in the log. The guard and the host know what is missing.

Do we need new readers for this?

A barcode and QR scanner that works like a keyboard is enough. InnerWeb is a software producer, not a device manufacturer.

See the QR gate in action

We will show the technician visit flow from invitation to the entry log entry, on a scenario close to your plant. Book a short conversation with the InnerWeb team.

Let's talk