InnerWeb
Skip to main content

Missing risk added in the hall map editor: a scenario for the site administrator

A site administrator is tidying up the hall map and notices a hazard that is not in the risk catalogue. Instead of reporting it by email and waiting, they add the risk in the map editor, and it immediately lands at the right hall level. Below is the step-by-step scenario, with the decisions worth making along the way.

4
levels of the location hierarchy: hall, area, line, place
Source: feature card
5
steps in the scenario of adding a risk
Source: sample calculation

Starting point: the hall map exists, but one hazard is missing from the catalogue

We describe a deployment scenario for a plant that manufactures agricultural machinery and belongs to a global group. This is a concept based on the system functions, not a description of a completed project. The hall already has a map in the editor and its levels are named: hall, area, line, place. The risk catalogue was populated at start-up, but nobody anticipated everything that happens at the workstations.

The site administrator goes through the map levels to tidy up the names. Next to one of the lines, the left column shows the risks of every level on the path of the selected node, from the hall down to the place. A hazard is missing, one that shift workers know from their daily work but that never made it into the catalogue. Without the tool, they would have to describe the problem in an email to IT or to the OHS team and wait for the dictionary to change.

The solution: the risk is created where the problem is

The administrator and the OHS role create the new risk in an editor shared with the dangerous work settings. The missing hazard is entered once, and from that moment every authorised user can select it. In the map editor, risks are shown as a list, one per row: pictogram, name, protective measures. A risk created in the level window is assigned to that level straight away, so there is no second step of searching for it in the catalogue.

The risk card contains a name in Polish and in English, a description, a pictogram, a list of preventive measures, and an assessment of probability, exposure and severity before and after the measures are applied. There is always exactly one pictogram, with no option to leave it blank, which forces the choice of a clear hazard symbol. The risk assessment is prepared and approved by a person: the system documentation does not describe any automatic assessment by artificial intelligence.

The administrator's sequence of actions

The practical sequence takes about fifteen minutes and does not require leaving the map editor. The list below arranges it so that each step can be checked on screen.

  • Select the map node where the hazard appeared and check the risks of all levels on the path.
  • Make sure a similar risk does not already exist under a different name before you create a new one.
  • Create the risk in the level window: name in Polish and English, description, one pictogram.
  • Add the preventive measures and assess probability, exposure and severity before the measures and after them.
  • Save and check that the tile shows the new name and the new symbol.

Time from noticing a hazard to showing it to the contractor

Time from noticing a hazard to showing it to the contractorBar chart: 48 hours when reporting to the IT department versus 1 hour when adding the risk in the map editor.01020304050hoursReport to IT: 48 hours48 hoursReport to ITAdding in the editor: 1 hours1 hoursAdding in the editor
Source: Sample calculation based on the assumptions in the section on results; times to be replaced with the plant's own measurements

Why the editor reloads the catalogue after saving

After a risk is saved in the map editor, the catalogue is reloaded by force. The reason is practical: a tile on the map must not show the old name and the old symbol, because the administrator would then conclude that the change was not saved and create a duplicate. For the user this is one thing less to check by hand, and for an auditor it is proof that the list of risks visible on the hall floor is up to date.

The 3D map editor is available to the administrator role, so changing risk assignments to hall levels does not require a separate permission. In a plant where OHS and administration are different people, this leads to a simple rule: the administrator works on the map, and OHS approves the content of the assessment and the measures. We describe the separation of roles in more detail in the recommendations on editing permissions for the catalogue.

Result: one entry, visible across the whole hierarchy

The result of the scenario is a shorter path from noticing a hazard to showing it to the contractor. The risk catalogue is hierarchical, and risks are assigned to locations at every level as well as to the type of dangerous work. A new risk entered once can be used on a line, in an area and in a work type, provided an authorised person assigns it there.

The example calculation below compares the route through a report and a dictionary change with adding the risk in the editor. The assumptions are explicit, and the times should be replaced with the plant's own measurements.

Conclusions for a plant that starts with the map

The first conclusion: the catalogue does not have to be complete on the day of start-up. It is worth giving the administrator and OHS the right to add risks while they tidy up the map, instead of postponing the topic to the next review. The second conclusion: a risk is an element of the global catalogue, so a later change to its description applies everywhere it is used. We discuss this rule in the implementation notes on global risks.

The third conclusion concerns evidence: every added risk has protective measures and an assessment, so during an audit you can show not only the hazard itself but also the way it is limited. The system supports documentation, and the decision on the risk level is taken by the designated person.

Example calculation

Reporting route versus adding the risk in the editor

Assumptions
ParameterValue
Email routing time through IT and OHS48 hrs
Time to add the risk in the editor1 hr
Number of missing risks in the first quarter12 risks

Result: With 12 missing risks, the difference is 12 x (48 - 1) = 564 hours of waiting time during which the hazard was not shown to contractors.

Note: Sample calculation. This is calendar waiting time, not person-hours; the assumptions need to be confirmed at the specific plant.

Checklist

Video

Frequently asked questions

Who can add a risk in the map editor?

The 3D map editor is available to the administrator role, and risks are created by the administrator and the OHS role. A requester in the context of a permit can add a risk to that particular permit, but cannot assign it to a dangerous work type.

Is the new risk immediately visible to others?

Yes. A risk entered once goes into the catalogue, from which every authorised user can select it. A risk created in the level window is assigned to that level straight away.

Does the system assess the risk level on its own?

No. The assessment is prepared and approved by a person. The editor calculates the level from the entered values and shows it as a marker, but it does not make the decision in place of OHS.

We will show the map editor on your hall

Book a conversation or a demo: together we will walk through the path from a noticed hazard to a risk shown on the permit printout.

Let's talk