InnerWeb
Skip to main content

OHS digitalisation in a plant: a step-by-step guide

OHS digitalisation starts with an inventory of paperwork, not with choosing software: a plant that knows how many forms, registers and summaries it has picks modules more accurately and finishes the pilot faster. Below are four implementation stages, an illustrative calculation and a list of what must be ready before the first login.

PLN 0
additional licence fee for modules within the same licence
26 h
monthly time saving in the illustrative calculation
Source: illustrative calculation

Why paper stops being enough

OHS documentation in an industrial plant is scattered across binders, spreadsheets and mailboxes. Each of these places works separately, so when management asks how many hazards are open in a department, the answer is a manual summary that is out of date the day it is sent.

The second problem is evidence. An auditor, an inspector or an insurer asks not only whether an inspection took place, but when, who carried it out, what they found and who closed the defect. Paper allows this to be reconstructed, but at the cost of hours of OHS staff time. A system that records these events in one place provides audit evidence without assembling it from scratch.

Digitalisation does not replace inspections carried out by the OHS service or change the employer's obligations. It changes how the result of that service's work is recorded, passed on and reported.

Stage 1: inventory of paperwork

Before you choose modules, list the documents that circulate in the plant today. For each, establish four things: who fills it in, who approves it, where it is kept and how often it is used. The inventory usually takes a few working days and incidentally gives you a list of forms that nobody has read for years.

  • Reports of hazards, defects and near misses: forms, boards, e-mail messages.
  • Checklists from OHS walkarounds and inspections: who keeps them, in what cycle, where the results go.
  • Registers of training and validity of qualifications: separately for plant employees and for external firms.
  • Summaries for management: who compiles them by hand, from what sources and how long it takes.
  • Documents and instructions assigned to workplaces: hall, area, line.

Sample OHS digitalisation schedule

Sample OHS digitalisation scheduleHorizontal bar chart of four OHS digitalisation stages in weeks: 2, 3, 6 and 8.02468weeksInventory of paperworkInventory of paperwork: 2 weeks2Module choice andconfigurationModule choice and configuration: 3 weeks3Pilot in one departmentPilot in one department: 6 weeks6Rollout to further departmentsRollout to further departments: 8 weeks8
Source: Illustrative calculation: indicative assumptions for a medium-sized plant

Stage 2: choosing modules and scope

The InnerWeb platform runs as a single instance with a single user account, and further modules are switched on within the same licence, without a new installation. A single licence includes, among others, gatehouse verification, walkarounds and inspections, defect and event reports, tasks and documentation, and reports with a management dashboard. The additional licence fee for simply switching on another module is zero zlotys. The cost grows only when you order configuration and training for a new scope.

We recommend starting with the narrow scope that hurts most and leaving the other modules for later stages. In practice this is most often hazard reports and OHS inspections, because they give a quick, measurable effect and do not require the whole workforce to change habits.

Hazard and event reports

Every logged-in user can report a hazard, a defect or a near miss: with a location from the plant dictionary, a type, a description and photos. The report goes to the team that takes it over and closes it. For management this means one list of open matters instead of several sources that do not fit together.

OHS inspections with a checklist

One OHS checklist can be run at many sites, so results are comparable between sites and periods. A checklist item can be linked to a place in the hall and presence can be confirmed by BLE or a QR code. A non-conformity from an inspection becomes a report in one step. The system does not replace the inspection by the OHS service required by regulations; it only organises its record.

Walkarounds and checkpoints on a map

The plant defines checkpoints on a map, each with its own checklist, and combines them into routes per department. A document from the library can be attached to a checkpoint without copying the file. The functional scope of the walkaround module is agreed with the client at the planning stage, so that the pilot relies on elements that are actually ready in a given installation.

Stage 3: a pilot in one department

Run the pilot in one department or one hall, with a designated owner on the OHS side and an owner on the production side. A well-chosen department has several dozen people, clear checkpoints and a manager who sees the system as a help, not an extra duty.

Agree three success measures before the start and do not change them along the way: the number of reports per week, the share of reports closed by the agreed deadline, and the share of planned inspections that actually took place. Without these numbers the pilot ends with impressions, not a decision.

After the first two weeks, hold a short review with users: what gets in the way, what is missing from the location dictionary, which form fields are unnecessary. Introduce corrections immediately, because the pilot is the only chance to adapt the plant dictionary to the real language of the hall.

Monthly hours spent on summaries for management

Monthly hours spent on summaries for managementComparison of 40 hours of manual work per month with 14 hours after introducing recurring reports.010203040hrsBy hand from paper and spreadsheets: Summaries: 40 hrs40 hrsBy hand from paper and spreadsheetsFrom recurring reports: Summaries: 14 hrs14 hrsFrom recurring reports
Source: Illustrative calculation based on the assumptions in the section on OHS staff time

Stage 4: expansion and reporting

When the pilot delivers reliable numbers, expand the scope by department, not by module. The same configuration pattern, the same checklist, the same roles. Recurring reports generated daily, weekly or monthly arrive by e-mail with tables in the body and a PDF attachment with the plant's logo, and the location scope and recipients are set separately for each rule.

At this stage it is worth switching on further modules from the same licence, for example gatehouse entry control or tasks and documentation. Each requires configuration and training, but not a new installation.

Illustrative calculation: OHS staff time

The calculation below shows how to estimate the time saved, using a medium-sized plant as an example. The assumptions are explicit, so you can substitute your own numbers. It is not a promise of a result, only a way of counting.

Assuming 40 hours a month spent compiling summaries by hand and 14 hours after the introduction of recurring reports, the saving is 26 hours a month. At a rate of PLN 95 per hour this gives about PLN 2,470 a month, or about PLN 29,640 a year. The illustrative calculation does not include indirect gains, such as faster closing of defects or fewer repeats of the same report.

What to prepare before the first login

The most common reason for delays is not technology but a lack of organisational decisions. Settle them before the start: who is the administrator, who approves reports, who has access to reports, and what the location dictionary looks like. Roles and permissions in InnerWeb come from roles with inheritance and a scope matrix, so it is good to have them written down in advance.

  • A named list of administrators and process owners on the OHS and production side.
  • A location dictionary: halls, areas, lines, recurring points.
  • One shared OHS checklist to run in the pilot.
  • The date and format of training for users and approvers.
  • The three agreed pilot success measures and the review date.
Example calculation

Time saved on OHS summaries

Assumptions
ParameterValue
Time spent on manual summaries today40 hrs/month
Time after introducing recurring reports14 hrs/month
Hourly rate95 PLN/hr

Result: 26 hours a month, about PLN 2,470 a month, about PLN 29,640 a year

Note: Illustrative calculation on explicit assumptions; the result in a specific plant depends on the number of departments and the current way of reporting.

Video

Frequently asked questions

Where should OHS digitalisation in a plant start?

With a list of the documents that circulate in the plant today, stating who fills them in and approves them. On that basis you choose a narrow scope for the pilot, usually hazard reports and OHS inspections.

Does every additional module mean a new licence?

No. Modules run on the same instance and in the same licence, without a new installation. Switching on a further scope requires configuration and training, but not an additional licence fee for the module itself.

Does the system replace the OHS service's inspections?

No. Inspections in the system organise the record and results, but the inspection required by regulations remains the duty of the OHS service and the employer.

How long does a pilot take?

In the illustrative calculation we assume several weeks in one department, with a review after the first two. The time depends on the number of users and the readiness of the location dictionary.

Plan an OHS digitalisation pilot

Let us discuss the scope of a pilot in one department of your plant. We will show what reports, inspections and summaries look like on data close to your own.

Let's talk