InnerWeb
Skip to main content

Service permit template: implementation notes

The service permit template is created in the installation data, not in code, so the data administrator can set it up without the developers. Below is the configuration order for machine locations: preparatory, main and closing tasks, and auto-closing, together with the pitfalls that show up only in use.

4
task types in the template: preparatory, main, closing, auto-closing
Source: card

What is the template and what is data

The flow of the permit follows a template linked to the location and its tasks. The configuration sits in the installation data, not in the code, so changing the template does not require deploying a new version of the application and does not go through the software change process.

The data administrator is responsible for three things: the set of tasks, their order and their assignment to locations. Approving permits and tasks is a separate role on the plant side.

Order of configuration

The safest way is to configure the template from the end of the process to the beginning: first define what finishing the work means, then build what leads to it.

1. Closing tasks

Define what must happen before closing: cleaning the place of work, restoring guards, acceptance by the plant. These are the tasks that protect the plant after the technician has left.

2. Preparatory tasks

Set up the tasks that the plant carries out before the main work: stopping the machine, preparing the place, confirming qualifications. The plant closes the preparatory tasks, so the list should be short and unambiguous.

3. Main tasks

Describe the technician's work in a way that can be closed with a single action. A main task that is too general invites closing it out of habit, and one that is too fine turns the permit into a twenty-item checklist.

4. Auto-closing

Enable it in the template where closing should happen automatically. The system closes the tasks and the permit once all tasks are closed and the workers have left the place of work. Enable it first for one machine and check whether the closings match reality.

5. Link to location and risks

Assign the template to the machine's location. Then the risks of that location appear on the permit automatically, and the printout includes them in sections with deduplication.

Sample time to configure the template for one machine

Sample time to configure the template for one machineHorizontal bar chart of sample configuration time: 1, 1, 1 and 2 hours.012hrsClosing tasksClosing tasks: 1 hrs1Preparatory tasksPreparatory tasks: 1 hrs1Main tasksMain tasks: 1 hrs1Test and printoutTest and printout: 2 hrs2
Source: Sample calculation: one machine, times assumed for illustration

Pitfalls visible only in use

The first pitfall is auto-closing enabled too early: if the transmitters in the hall are spaced too sparsely, the system may consider the place of work empty while a person stands just beyond the boundary of the location. Roughly one transmitter per 100-200 m2 is typical in a building, and the position comes from averaging many signals, so the boundaries of the locations should be checked on site.

The second pitfall is the printout. The printout can mirror the plant's paper form through an uploaded template matrix, but the matrix has to be tested on a real document before the first use.

The third is the lack of separation of roles: the same user configures the template and approves the permits. Separating them makes the audit easier.

Test before going live

Before the template is made available to technicians, run one complete permit on a test location: create it, go through the tasks, leave the place of work and check whether auto-closing worked. Record the result, because it will serve as proof that the configuration is correct.

Maintaining the template after go-live

A template is not a document for all time. After each service ask the coordinator whether the tasks matched reality, and improve the template based on the answers. Since the configuration lives in the data, a correction does not require deploying code and can take effect immediately.

For order keep a short change log of the template: date, reason, person who made the change. This helps the audit and lets you go back to the previous version when a change proves wrong. If the plant has a paper form, also keep the printout matrix consistent with its current version.

When planning the schedule, leave time for two rounds of corrections after the first few permits. The first services always reveal a task that was missing, or one that nobody needs. It is best to invite the maintenance coordinator and a security representative to review the template, because they see the effects of the configuration in the hall. All numbers in the examples on this page are a sample calculation based on the assumptions given in the text, not data from a specific plant.

Video

Frequently asked questions

Does changing the template require a programmer?

No. The flow of the permit follows the template in the installation data, not the application code.

Where should the configuration start?

From the closing tasks, because they define what the end of the work means, and then the preparatory and main tasks are arranged.

When should auto-closing be enabled?

After a test on one machine, once the transmitters in the hall and the boundaries of the location have been checked on site.

Let's set up the template together

Book a configuration workshop: together we will arrange the tasks and test auto-closing on one machine.

Let's talk