InnerWeb
Skip to main content

Teams assigned to halls: best practices

In a production plant, a notification about an event makes sense only if it reaches a person who can respond at that location. Teams assigned to halls and lines tie responsibility to the plant map, not to the organizational structure. Below are practices for a maintenance manager who builds them from scratch or tidies up existing ones.

What a team is and what follows from it

A team groups the people responsible for parts of the plant. It has areas from the map tree (hall, area, line, location), members, roles in work and the report categories it supports. Teams decide who is assigned and notified in work permits, reports and location alerts, and the administrator manages them in settings.

For the maintenance manager this means the team structure is a tool for organizing work, not merely a list of people. If a team is badly built, an alert about a worker's inactivity in the paint shop may reach someone at the far end of the plant.

Team building practices

Good practices come down to four rules: a team describes an area, not a department; each area has an owner; each report category has an addressee; and changes are controlled.

Build from the map, not from the org chart

Start with the map tree: hall, area, line, location. For each level ask who actually responds when an event occurs. Teams are created from this list. The org chart helps only when choosing deputies.

Limit reports to the area where it makes sense

A team may have an option to limit reports to its own area. In large halls, where reports from other lines only distract, this option reduces noise and raises the chance that a report is picked up. In small plants it is better not to enable it, so that reports are not lost when staffing is incomplete.

Assign report categories

A team handles selected report categories. Make sure no category is left without an addressee, and none has several without an agreed order. An empty category means a report without a response.

Watch the default permit staffing

The issuer, approver and coordinator fields in a permit are filled in by default according to the team assigned to the location, and can be hidden per location. If a team is out of date, the default staffing will be wrong in every new permit for that location.

Sample calculation: recipients of an inactivity notification

Sample calculation: recipients of an inactivity notificationBar chart: a team by department notifies 25 people, of whom 3 are near the event; a team by hall notifies 6 people, of whom 5 are nearby.0510152025people notifiedTeam by department (Notified people): 25 people notified25Team by hall (Notified people): 6 people notified6Notified peopleTeam by department (Near the event): 3 people notified3Team by hall (Near the event): 5 people notified5Near the event
  • Team by department
  • Team by hall
Source: Sample calculation based on assumptions: a plant with 25 people in maintenance and six people on shift in the paint shop.

Teams of external companies

A team with the task approver role may consist only of external users. This is useful when a subcontractor working in the hall has its own coordinator responsible for performing the tasks. However, approval of particularly hazardous work remains on the plant side, so the external team does not replace the approver from OHS.

For companies that regularly work on site, it is worth setting a default contact person who acts as coordinator, so that alarms reach the right person on the company side.

Team review

Teams age faster than the role matrix: working shifts, lines and staffing change. A team review once a quarter, plus one after each line start-up or shutdown, is the minimum. In the review we check whether every area on the map has at least two people in its team, so that one person's absence does not stop the response.

Checklist

Video

Frequently asked questions

Who manages teams in the system?

The administrator manages them in settings. The composition and areas should be agreed with the process owner, because teams decide who is notified.

Can one person be in several teams?

It depends on the configuration of the installation. In practice it is worth limiting multiple memberships, so that a person is not burdened with notifications from several halls.

Can an external team approve particularly hazardous work?

No. Approval or rejection of particularly hazardous work is reserved for a user on the plant side.

Let's build teams by halls

In a demo we will show the map tree of the plant, the teams assigned to areas and the route of a notification from an event to a person.

Let's talk