Assumptions of the scenario
The plant manufactures farm machinery across several halls: welding, painting, assembly and a component warehouse. The pilot covers one hall with an isometric map and beacons, hazardous work permits built from templates, risks assigned to locations, and SOS and inactivity alarms visible to the dispatcher. Guest registration runs at a kiosk with a QR code from the invitation.
This scope touches three worlds: OHS owns permits and risks, maintenance owns work on machines and the response to events in the halls, and IT owns accounts, integrations and data security. Without an earlier split of responsibility, the pilot turns into a series of questions about who should approve what.
The scenario is a concept presented to the plant and does not describe a rollout running at a client. It serves to set the questions for the first workshops.
Teams as the core of the responsibility split
In the system, responsibility for part of the plant is expressed through a team. A team groups the people responsible for selected areas of the map tree (hall, area, line, location), and has members, roles in work and the report categories it supports. Teams decide who is assigned and notified in work permits, reports and location alerts, and the administrator manages them in settings.
For the hall pilot this means a concrete set: a welding team, a painting team, an assembly team and a maintenance services team. Each gets an area it answers for and a list of the report categories that concern it.
OHS: owner of permits and risks
OHS is responsible for permit templates, for assigning risks to locations and for verifying qualifications. A work permit requires signatures from the right people: the issuer, the approver and the work coordinator, and a check of employee qualifications.
Maintenance: performer and coordinator
In the scenario, maintenance most often acts as the issuer or the coordinator of work on machines. The issuer, approver and coordinator fields in a permit are filled in by default according to the team assigned to the location, which shortens document preparation and reduces errors in staffing.
IT: accounts, integrations, continuity
The IT department is responsible for accounts and for integrations with the plant's existing systems. InnerWeb works as an independent system that complements the client's systems (access control, time and attendance, HR, ERP), so the owners of those systems remain in the responsibility matrix and must be invited to a workshop.
Sample calculation: team preparation time in the pilot
Who approves and who performs
Approving or rejecting particularly hazardous work is reserved for a user on the plant side, not for the contractor. In the hall scenario this means the approver is a person from OHS or the area manager, and the external company doing the welding does not approve its own permit.
The system does not replace the person managing the works or the authorizing person: it enforces rules, and responsibility stays with the people named in the process. It is worth saying this clearly at the first workshop, because there is often an expectation that software will take over the decision. A team with the task approver role may, however, consist only of external users, which makes it possible to separate the team of a subcontractor responsible for performing the tasks.
Plan of three workshops in the pilot
The scenario assumes three short meetings where decisions are made, without pushing them into later weeks.
- Workshop 1: hall map and area tree. Participants: OHS, maintenance, hall manager. Output: list of areas and an owner for each.
- Workshop 2: teams and roles. Participants: OHS, maintenance, IT. Output: team composition, report categories, who approves permits.
- Workshop 3: accounts and integrations. Participants: IT and the owners of the access control, time and attendance and HR systems. Output: account list, administrator role, method of passing on events.
Scenario risks and how to limit them
The most common risk is teams built on the organizational chart rather than on halls. An inactivity alert from the paint shop then reaches a person with no influence over the location of the event. A team should describe responsibility for an area, not the name of a department.
The second risk is role drift between installations: the full list of roles depends on configuration, so copying settings from another plant without verification creates gaps. The third is the lack of one person who oversees the whole during the pilot. That role is described on a separate page about the safety process owner.
Video
Frequently asked questions
Does the system take responsibility away from the works manager?
No. The system enforces the rules of the process, and responsibility stays with the people named in the permit: the issuer, the approver and the coordinator.
Who should be in the team of task approvers?
A team with the task approver role may consist only of external users. Approval of particularly hazardous work stays on the plant side.
Does the pilot have to start with the whole plant?
No. The scenario assumes one hall whose areas and teams can later be copied to others, after the role configuration has been checked.
Let's plan the role split for your hall
We will prepare a pilot scenario with areas, teams and a list of workshop participants for your plant.
Let's talk