InnerWeb
Skip to main content

Responsibility split: plant and security agency

An OHS manager who puts the division of tasks between the plant and the security agency in writing quickly discovers that half the matters have no owner. Accounts, badges, refusal handling and closing alarms sit on the boundary. Below are six recommendations that assign each of these tasks to a specific role.

6
tasks in the responsibility matrix
Source: recommendations summary
1
supervisor required in the SOS template
Source: SOS alarm function card

Why put the split in writing

The security panel works on the principle of separated roles. Security has its own screen with five views, but not all the system's permissions. This is a good basis for dividing tasks, because part of the responsibility is already written into the structure of the permissions. The OHS manager's job is to add the rest.

The recommendations apply to a production plant where security is provided by an external agency. We assume the plant runs the panel and an SOS alarm on a watch. The split takes the form of a matrix: the task, the owner on the plant side, and the executor on the agency side.

Six tasks to assign

For each task we give a recommended owner and a justification that follows from how the system works.

1. Guard accounts: owner the plant, executor the administrator

The plant administrator creates and deactivates accounts based on the named list from the agency. The agency is responsible for timely reporting of changes in the team. When a guard leaves the agency, the notification must arrive on the day of departure, not a week later.

2. Badges: owner the plant, executor the office or reception

Every badge has a random, unguessable code. Revoking a badge issues a new one, and the history of badges is kept. The decision to revoke is taken by the plant, for example after a report of a lost badge. Security should only report the circumstances, not revoke badges on its own.

3. Reaction to a refusal: owner the plant's security manager, executor the guard

When access is refused, the panel shows a red banner and plays a voice recording. The guard applies the rule: does not let the person in and informs them of the missing element. The plant is responsible for making sure the missing element can be quickly completed, for example through training or a permit. The refusal leaves a trace in the register, and the plant analyzes this register every week.

4. Work permits for today: owner the permit owner, security reads

The work permits for today view is read-only for security: security does not suspend, resume or close permits. The split is therefore clear: the plant manages permits, and security checks who may enter today. Write this into the matrix as the limit of the agency's responsibility.

5. SOS alarm: receipt by the plant or the duty person, closing by the supervisor

The SOS alarm on the watch creates its own alarm permit, starts the rescue chain in the messenger and by phone through the PBX, and lasts until a person closes it. The alarm permit can be closed by the supervisor assigned to the SOS template. If the template has no designated supervisor or owner, nobody except the person in distress can close the alarm. The plant must therefore name a supervisor in the template, and the agency must know who it is, so that it calls the right number.

6. Employee movement and the alarm: owner the plant

Employee movement does not cancel the SOS alarm, and a second press of SOS on an open alarm permit does not create a duplicate or a second notification. The guard should not assume that a moving employee is safe. Write that the alarm is closed after confirmation by the supervisor, not after observation from the gate.

Task owner in the matrix (six tasks)

Task owner in the matrix (six tasks)Donut chart of the split of six tasks between the plant, the permit supervisor and the agencyPlant: 4 tasks (66.7%)Permit supervisor: 1 tasks (16.7%)Security agency: 1 tasks (16.7%)6tasksPlant4 tasks (66.7%)Permit supervisor1 tasks (16.7%)Security agency1 tasks (16.7%)
Source: Sample calculation: assignment of the six tasks from the recommendations

Contractor invitations: a shared task with caution

Security may invite an employee of an external company to a permit and confirm their arrival from the panel, but the list to invite from comes from the company assigned to the permit. We recommend writing into the matrix that invitations from the panel are allowed only for permits assigned by the plant, and that the agency does not add companies or people from outside the list.

How to keep the split working in practice

It is worth posting the matrix at the security post and reviewing it once a quarter with the shift manager. At a change of agency or of the guard team, the matrix is the starting point for training. A test of whether the split works is simple: for each task, ask who will do it at night on a Sunday, and check whether that person knows it.

Video

Frequently asked questions

Can the agency revoke a badge?

We recommend the decision is taken by the plant. The agency reports the circumstances, and revoking issues a new badge and keeps the history.

Who closes an SOS alarm?

The supervisor assigned to the SOS template. If the template has no supervisor, nobody except the person in distress can close the alarm.

Can security suspend a permit?

No. The work permits for today view is read-only for security.

Setting up a task split with security?

We will help turn the panel permissions into a responsibility matrix. Let's arrange a call.

Let's talk