Start with paper, not with the system
The first step does not happen in the system. The administrator draws the tree on paper: the plant, the district or department, the site, and within the site the elements where something happens, for example the chamber, the tank, the switchgear. The layout should reflect how people actually talk about the sites, not only the organisational chart.
Only once the tree has been reviewed with the head of maintenance and the person responsible for occupational health and safety is it worth entering it. Changing the layout after the first entries have been made is possible, but it makes comparisons over time harder.
Inheritance: the instruction once, applying down the tree
Documents, audio and video are assigned at every level of the plant hierarchy, for example hall, area, line, with inheritance down the tree. A document can also be attached to an item on a checklist. For a water network, this means that the instruction for work in a confined space needs to be assigned only at the district level, and the sites below will inherit it automatically.
This saves work, but requires discipline. An instruction specific to one site, for example a particular way of isolating the power supply, is assigned at the level of that site. Otherwise a technician at another pumping station will see a document that does not apply to them.
- shared instructions: district or plant level
- site instructions: site level
- document attached to a checklist item: only when it concerns a specific step
- video and audio: the same as documents, with inheritance down the tree
Sample calculation: number of instruction assignments
Checkpoints and round routes
The plant defines round checkpoints on the map, each with its own checklist, and groups them into routes per department. For a water network, a department may mean the district of pumping stations or a group of stations served by one crew.
Occupational health and safety inspection items can be linked to a repeating checkpoint, with the location confirmed by BLE or QR. At a site without a transmitter network, a QR code at the checkpoint is enough. Where transmitters are installed, confirmation may come from location. The choice depends on the site, not on the requirements of the system.
Permits and external companies in the structure
A permit is tied to the place where the work is done. If the tree is well organised, a permit for replacing a pump goes to the right pumping station, and the dispatcher sees it together with other jobs in the district. The request of an external company and the permit issued to the contractor work on the same permit, visible on both sides.
When a permit is created, the system checks the permissions of the assigned workers. That is why it is important for the administrator to know who in the external company sets up accounts and how their qualifications are maintained.
The change log as protection for the structure
Changes to permits, the taxonomy of hazardous work, training results, automation rules and inspection routes are saved with their author and time. For the structure of sites this matters: when someone moves a site to another district, the round route and access to documents change, and the log shows who did it and when.
Decide who may change the tree. Ideally two or three people with a deputy, not all the district managers.
Pitfalls that surface after a few months
The first pitfall is a structure that is too fine-grained: a site split into ten elements of which only two are used. The second is names changed without order, so that the same site appears under three names. The third is documents assigned at too low a level and copied by hand.
Before launch, check on the plan that each site has one place in the tree, one name and the right level of instruction. We describe the details of organising the entry register on the page about the service entry register.
How many instruction assignments inheritance saves
| Parameter | Value |
|---|---|
| Number of sites | 40 sites |
| Shared instructions | 6 instructions |
| Number of districts | 5 districts |
Result: Without inheritance: 40 x 6 = 240 assignments. With inheritance at district level: 5 x 6 = 30 assignments.
Note: Sample calculation on the utility's own assumptions; the actual number depends on the plant's structure.
Video
Frequently asked questions
Can the structure be changed after launch?
Yes, but a change makes comparisons over time harder and changes routes and access to documents. Changes are recorded in the log with author and time.
Where should a shared instruction for all pumping stations be assigned?
At the district or plant level. Sites below will inherit it automatically.
Does every round checkpoint need a transmitter?
No. Location confirmation can come from BLE or from a QR code at the checkpoint.
Who should change the site tree?
A narrow group of administrators with a deputy, because changes affect routes, permits and access to documents.
Let's draw the tree of your sites together
We will help you translate the plant's structure into the hierarchy in the system and point out where inheritance will save the most work.
Let's talk