InnerWeb
Skip to main content

Safety process owner: 7 recommendations

Before a safety system pilot starts, the plant director should appoint one person who answers for the process from start to finish. This is neither the technical administrator nor the vendor, but a person on the plant side with decision rights. Below are seven recommendations on how to choose that person and what permissions to grant.

Who these recommendations are for

These recommendations are addressed to the plant director or to the person who decides when the pilot of the permit, guest registration and location system starts. They apply to production plants where several departments are involved in the rollout: OHS, security, maintenance, IT and HR.

The process owner is the person who settles disputes over scope, approves changes to roles and answers to the management board for the operation of the whole. In the system there is a counterpart in the form of a broad-scope role, but organizationally this function is wider than any single account.

Seven recommendations

The recommendations follow an order: first the choice of the person, then their place in the system, and finally the maintenance rhythm. Each can be implemented on its own, but together they form a coherent model of responsibility.

1. Choose a person with decision rights, not availability

A common mistake is naming someone who has time rather than someone who has decision rights. The process owner should be the OHS manager, the plant director or the maintenance manager, someone who can tell purchasing or IT that a change is necessary.

2. Link the role to a role in the system

Permissions in the system follow from inherited roles and from the scope matrix that defines the access level for each area. Editing and deleting internal accounts is reserved for the administrator, the manager and OHS, so a process owner from one of those groups has a full path to managing accounts.

3. Separate the process owner from the technical administrator

The e-mail settings tab for external companies is available only to the administrator, and the protection is a role requirement in the API, not merely hiding the option in the interface. The technical administrator from IT carries out these settings, but the process owner decides which notifications should reach the companies.

4. Give them the right over teams

Teams decide who is assigned and notified in permits, reports and location alerts. The process owner should approve the team composition and the areas each team answers for. The administrator makes the change in settings, but every change requires the owner's approval.

5. Name a deputy

Leave, illness or a change of position of the owner must not stop the process. We recommend naming a deputy with the same role in the system and recording them in the responsibility split document.

6. Set a review rhythm

The process owner should review roles and teams at a regular rhythm, for example once a quarter, and after each reorganization or change of hall. The review ends with a short note of decisions for internal audit.

7. Leave the owners of systems with separate responsibility

InnerWeb works as an independent system that complements the client's existing systems: access control, time and attendance, HR and ERP. The safety process owner does not take over responsibility for those systems, but must know their owners and know when to involve them.

Sample calculation: accounts with full scope

Sample calculation: accounts with full scopeBar chart: without the rule there are 11 accounts with full scope, with the minimum permissions principle there are 3.0246accountsWithout a rule (Owner): 1 accounts1With the minimum permissions principle (Owner): 1 accounts1OwnerWithout a rule (Administrators): 4 accounts4With the minimum permissions principle (Administrators): 2 accounts2AdministratorsWithout a rule (Hall managers): 6 accounts6With the minimum permissions principle (Hall managers): 0 accounts0Hall managers
  • Without a rule
  • With the minimum permissions principle
Source: Sample calculation based on assumptions: a plant with six halls where, without the rule, hall managers receive broad accounts.

What permissions to give the process owner

The minimum permissions principle applies to the owner too. They should have access to reviewing roles, teams and permits, and leave technical tasks, such as configuring integrations, to the administrator. Where the owner role is combined with an OHS, manager or administrator function, they also receive the right to edit and delete internal accounts.

A good practice is to limit the number of accounts with full scope to one owner, one deputy and one technical administrator. Each additional account with full scope increases the surface for errors and makes audit harder.

Common mistakes we observe

In plants where no process owner has been named, responsibility dissolves between OHS, security and IT. The rollout team receives conflicting instructions, and the first permits are configured differently in each hall.

The second mistake is naming the system vendor as process owner. The vendor advises and trains, but decisions about roles and teams must stay on the plant side.

Video

Frequently asked questions

Can the IT department be the process owner?

It can be the technical administrator, but the process owner should belong to the area responsible for safety, for example OHS or plant management, because that area answers for the consequences of decisions.

Does the owner need an account with full scope?

No. The scope needed to review roles, teams and permits is enough. Editing and deleting internal accounts is reserved for the administrator, the manager and OHS.

How often should roles be reviewed?

We recommend once a quarter and after each reorganization, change of hall, or departure of a person holding a broad-scope role.

Let's appoint the process owner before the start

We will help prepare a short responsibility split document, to be signed by the plant director.

Let's talk