InnerWeb
Skip to main content

Hot work in the paint shop: a machinery plant scenario

A concept for a machinery manufacturer where the maintenance manager must carry out welding next to a paint booth, and the location risks, the approval and the post-work watch have to come together in one permit. We describe an implementation scenario based on the behaviour of the system as documented in its feature documentation, not a completed installation.

3 h
minimum watch time before closing
Source: karta
5
risk sections on the printout, without repetition
Source: karta
4 h
extended watch stage
Source: karta

Starting point: repair work next to a paint booth

The scenario concerns a machinery plant for agricultural equipment owned by a global group, at the offer and system demo stage. The paint shop stands next to the assembly hall, and an external contractor has to replace a load-bearing structural element beside a booth. This requires welding, which is hot work, in a place where solvent vapours, paint and flammable materials are present.

This is a concept, not a description of an implementation. We show how such work could pass through the system if the plant configured it according to the feature documentation. Every statement about how the system behaves is based on that documentation, and the figures are based on stated assumptions in an example calculation.

The organisational problem is typical. The paint shop risks are known to the health and safety manager, the welding procedure is known to the contractor, and the watch period after the work is remembered only by whoever happens to be on shift. When these three things live in three places, the first casualty is the watch, because it ends after the main job is already over.

One permit, three layers of responsibility

In InnerWeb, particularly hazardous work (PSZN) requires a check of the contractor's competence, approval by a user on the plant side and, for hot work, a watch period after the work ends. For the paint shop this means three layers that the manager sees in one place instead of in three documents.

The first layer is the location risks. The plant assigns risks, together with the required protective measures, to the paint shop and its areas, and also to the type of hazardous work. Whoever issues a permit for welding next to a booth gets the location risks and the work-type risks on the printout without manual retyping.

  • Location layer: risks assigned to the hall, area, line or specific place, for example the presence of solvent vapours next to the booth.
  • Work layer: risks and measures assigned to the type of hot work, regardless of where the work takes place.
  • Approval layer: the decision of the user on the plant side, which an external contractor cannot make on their behalf.

Why the plant approves, not the contractor

Only a user on the plant side can approve or reject a PSZN. The external contractor submits the request and carries out the work, but does not close the decision loop. In a paint shop this matters in practice: the plant knows the current state of the booth, the line's operation and the neighbouring jobs.

Times in the watch path after hot work

Times in the watch path after hot workBar chart: stage 1 lasts 1 hour, the minimum before closing is 3 hours, the extended stage lasts 4 hours01234hStage 1: 1 h1 hStage 1Minimum before closing: 3 h3 hMinimum before closing4-hour stage: 4 h4 h4-hour stage
Source: Feature documentation: particularly hazardous work and risks

Printout without repetition: how the risks combine into one document

The permit printout combines the risks in five sections without repetition: risks between permits, location hierarchy, additional locations, type of hazardous work and user risks. If the same risk appears at several levels, it appears once on paper.

In the paint shop scenario this solves a specific problem. Welding next to a booth touches the risks of the hall, of the paint shop area and of the type of work itself at the same time. Without automatic merging, the printout would list more than a dozen items, some of them repeated, so people stop reading them. With risks assigned to the right level of the hierarchy, the document is shorter and every item has a reason to be there.

One PSZN can have one type and several subtypes. In this scenario the type is hot work, and the subtypes can include welding and cutting carried out at the same time, without opening two separate permits.

Fire watch after hot work: 1 hour, 4 hours, minimum 3 hours

For hot work the watch path applies: a 1-hour stage, then a 4-hour stage, and closing is blocked until at least 3 hours of watch have elapsed. The system does not let you close hot work on judgement, because the timer runs on the server.

The watch is carried out by an employee of the external contractor, and moving to the 4-hour stage is possible only one hour after the watch starts. In a paint shop this matters for one reason: a smouldering ignition source near a booth shows itself after some time, not at the moment the arc goes out.

There is an additional lock on closing. A PSZN cannot be closed while more than one person remains on site. For the manager this means the permit stays on the open list until the team has really left the place.

  • Stage 1: the first hour of watch after welding ends.
  • Stage 2: the watch extended to 4 hours, available after one hour from the start.
  • Closing condition: at least 3 hours of watch and no more than one person on site.

The scenario step by step

The order below is a concept that the plant can reproduce in a demo or pilot. It assumes that the paint shop risks and the hot work type are already entered, because without this configuration the system has nothing to build the printout from.

The maintenance manager issues the parent permit for the repair and attaches a PSZN of the hot work type. The system selects the location and work risks. After approval by a user on the plant side, the contractor starts the work, welds and finishes. From this point the watch runs: the external contractor's employee stays at the work place, the shift manager sees the stage, and closing waits until the minimum time has passed.

What the team must have ready before the demo

The most common reason a demo goes badly is empty data. A system built on risks and templates shows its value only when someone has described the paint shop beforehand. It is worth doing this before the meeting, not during it.

The set is small and the effect is visible at once: the first permit printout for the paint shop already has the risks and protective measures, and the maintenance manager can see where they came from.

  • Location hierarchy: hall, paint shop area, line, place next to the booth.
  • Risks and protective measures assigned to the paint shop and to the type of hot work.
  • A person on the plant side authorised to approve PSZN.
  • An employee of the external contractor appointed to keep watch after the work.

Checklist

Video

Frequently asked questions

Can the contractor approve hot work on their own?

No. Only a user on the plant side can approve or reject a PSZN. The contractor submits the request and carries out the work.

Can the permit be closed after a shorter watch?

Closing is blocked until at least 3 hours of watch have elapsed. Moving to the 4-hour stage is possible only one hour after the start.

Does this description mean a completed implementation in the paint shop?

No. It is a concept scenario for a machinery manufacturer, based on the feature documentation of the system and at the offer stage.

Let us reproduce this scenario in your paint shop

We will prepare a demo of a hot work permit using your plant's data: risks, approval and watch in one run. We invite you to talk.

Let's talk