InnerWeb
Skip to main content

Working with a security company at the plant: best practices at the gate and for alarms

The plant's security manager and an external security firm work at the same gates but are responsible for different things. Good practice comes down to a clear split of roles in the system, shared procedures for QR and card checks, and transparent alarm escalation.

2
scan methods in the security panel: QR and RFID card
Source: product documentation

Why the split of roles at the gate needs to be written down

A plant usually employs its own security manager, while the gate is staffed by an external security firm. A security firm employee makes the decision each day on whether to admit a person, but the admission rules are set by the plant. When those rules are not written in the system, decisions at the gate depend on individual judgement and are hard to explain later.

A system in which the security panel bases its verdict on valid training, qualifications and permits moves the rules out of the head of the person on duty and into the configuration. The security employee follows the procedure, and the plant's security manager is responsible for its content.

Practice 1: separate roles for the plant and for the agency

Roles in the system and the permissions matrix let you configure access for administrators, security, OHS and the coordinators of external companies without any change to the code. We recommend separating the role of the plant's security manager, who can change the configuration and review reports, from the role of the agency employee, who only scans and confirms passages.

This separation has two benefits. It reduces the risk of an accidental change to settings at the gate, and during an audit it shows who had permission to perform a given action.

Sample alarm escalation: response time thresholds

Sample alarm escalation: response time thresholdsColumn chart: alarm response thresholds of 3 minutes for gate security, 5 minutes for the dispatcher and 8 minutes for the shift manager02468minutesGate security: 3 minutes3Gate securityDispatcher: 5 minutes5DispatcherShift manager: 8 minutes8Shift manager
Source: Sample calculation: thresholds to be agreed with the plant; illustrative values (sequence 3, 5, 8)

Practice 2: one procedure for QR and card checks

The security panel scans a QR badge or an RFID card and shows a verdict on whether the person may be on the site. The security employee does not have to remember the requirements for each group. It is enough to act in line with the verdict and the procedure for disputed cases.

Write down in the procedure what the security employee does when the verdict is negative: whom they report to, whom they inform and where they record the event. The procedure should be short, printed at the workstation and known to every shift.

Practice 3: explicit alarm escalation

An alarm in the system is useful only when someone receives it and it is clear what to do next. Decide which alarms are received by security at the gate, which by the plant dispatcher and which by the shift manager. Describe the time thresholds for escalation to the next recipient.

When the plant network blocks outbound traffic from the application host, webhook alarms are stored durably in a queue, and an external poller collects them over an inbound channel and delivers them onward. This way an alarm is not lost. It is worth describing this in the documentation for security, so that staff know a delay does not mean a lost report.

Practice 4: integration with the access control system

InnerWeb does not make or replace access control readers. It integrates with the client's existing access control system, and the partner may be the installer of that system. If security already works on the access control panel, the new system should add useful information to it rather than force work on two screens without need.

When designing the workstation, ask security which data they need within a few seconds: the photo, the validity of permits, the zone. The remaining information can be available after expanding.

Practice 5: an audit trail instead of memory of a change

The audit trail records changes to selected data together with the author and the time. For cooperation with an agency this means that if there is a dispute over who changed a permission or confirmed an entry, the answer comes from the record, not from witness accounts.

Agree in the contract with the security firm that data from the system may be used to settle events and for audits, and who has access to it.

Checklist

Video

Frequently asked questions

Can a security employee change permissions?

It depends on the role. We recommend that the plant's security manager changes the configuration, while the agency employee only scans and confirms passages.

What happens to an alarm when the network does not pass outbound traffic?

Webhook alarms are stored durably in a queue, and an external poller collects them over an inbound channel and delivers them onward. The alarm is not lost.

Does the system replace the access control system?

No. InnerWeb integrates with the existing access control system and does not replace readers.

Let's set the security roles in the system

We will show the security panel and the permissions matrix using an example of your gate. Book a call or a demo.

Let's talk