Scenario: morning shift at the warehouse gate
The concept applies to a logistics plant with one gate for vehicles and one for pedestrians. At six in the morning a contractor crew that services the loading docks enters the site. Some people hold a current introductory training, and some are only starting it, because they were assigned to work the previous day. The described sequence is a scenario based on the notification function, not a report from a specific plant.
The access control system passes on card readings, and InnerWeb matches them against qualifications. For each person without valid training a missing-training event is created. Without aggregation, the contractor coordinator would receive as many messages as there are untrained people, at intervals of a few seconds.
Problem: a flood of alarms teaches people to ignore them
The first alarm is useful, the tenth is noise. A coordinator who receives fifteen calls and e-mails about the same problem within five minutes soon stops reading them. Then the right message, that someone is really entering the loading dock without training, gets lost among the repetitions.
The second problem concerns the channels. A missing-training notification goes to the contractor coordinators by phone, e-mail and team messenger. Multiplied by the number of people at the gate, this would produce hundreds of messages per shift.
Number of messages to coordinators per shift
Solution: one 55-minute window per company
The missing-training alert at the gate is grouped per contractor company. The aggregation window is 55 minutes, and a repeat notification to the same company follows no sooner than 55 minutes later. In practice the first event opens the window, further scans from the same company go into the same summary, and the coordinator receives one message with a list of people.
As a result, the number of notifications depends on the number of companies, not the number of people. Two companies at the gate mean two summaries, even if there were fifty scans.
Sample calculation of message volume
Assumptions: 3 contractor companies on the shift, 36 people in total without valid training, 3 notification channels, a shift lasting 8 hours. Without aggregation: up to 36 events times 3 channels gives 108 messages. With the 55-minute window: for each company about 9 windows in 8 hours in the worst case, so up to 27 windows times 3 channels gives 81 messages, but only if the lack of training lasts the entire shift. In the typical case, where gaps occur in the first hour, each company receives 1 summary and together 9 messages.
What the coordinator does after receiving the summary
A summary makes sense only if the coordinator knows what to do with it. The scenario assumes three actions: sending untrained people to the training point, completing the training on a phone from the link, and confirming the final list of people admitted to work.
A repeat notification follows no sooner than 55 minutes later, so the coordinator has time to react. If the same problem still exists after the window has passed, the coordinator receives another summary, this time with the current list.
- send untrained people to the training point at the gate
- ask them to complete the training from the link on a phone
- verify which people have disappeared from the list after training
- report to the plant dispatcher those who entered without training
Audit trail instead of memory of the shift
Sent notifications are stored in the registers, so the plant has proof that the contractor was informed about the lack of training and when. For the safety manager this is an argument in a conversation with the contractor: the message does not get lost in private mailboxes, and its time is recorded.
The system supports the requirement to supervise contractors here, but it does not replace human decisions. Passing information to the coordinator does not relieve the plant of its duty to control entry.
Conclusions for the safety and protection manager
The 55-minute window is a compromise between speed of reaction and resistance to noise. After the pilot the plant can assess whether companies respond within that time, and only then consider changing the settings. The most important thing is that coordinators are assigned to the company with working channels: phone, e-mail and team messenger.
Before the start it is worth checking that each company has at least one coordinator with an active channel. A company without a coordinator will not receive a summary, and the gate will then generate events with no recipient.
Video
Frequently asked questions
Does the 55-minute window apply to the whole plant or to each company separately?
To each contractor company separately. The alert is grouped per company, so two companies receive two independent summaries.
Through which channels does the coordinator receive the alert?
By phone, e-mail and team messenger, provided these channels are configured for the company.
Does the alert replace the control at the gate?
No. The alert informs the coordinator and records a trail, but the decision to enter the site remains with the plant.
Check the grouped alert at your gate
We will show you what a summary of training gaps for a contractor company looks like and select the channels for coordinators.
Let's talk