Starting point: the readers stay
InnerWeb is an independent system that complements the client's existing access control, time recording, HR and ERP systems. InnerWeb does not produce or replace access control readers. It integrates with the client's access control system. Swipe events flow from the existing system to InnerWeb, and the evacuation list uses them without any change to the hardware at the doors.
A three-shift plant gains twice over: it does not stop the readers during a replacement and the workforce keeps the way they swipe their cards today.
What the evacuation list does
The evacuation list refreshes every 13 seconds and divides people into groups, including separate tabs for each external contractor. In a multi-shift plant this means the evacuation coordinator at night sees the night crew and external contractors, not everyone who has swiped a card at any time during the day.
For plants where halls may contain explosive atmospheres, Directive 1999/92/EC sets minimum requirements for the health and safety protection of workers potentially at risk from such atmospheres. A reliable list of people is one of the elements that support the response to an incident.
Example number of people on the list over 24 hours
Shift handover and forgotten exits
The hardest moment is the handover between shifts: some people are still leaving, some are arriving, and swipes appear with a delay. At that time the evacuation list shows more people than at other times of day, so the list has to be read with care.
Forgotten exits inflate the list. It is worth setting a plant rule that the person finishing a shift swipes out, and that the shift supervisor checks for anomalies before the final patrol.
Night shift and long stays
During an extended shift or a maintenance shutdown, people stay in the plant longer than usual. Rules for removing entries after a long stay should be assessed against the actual shift roster, so that the list does not lose people who are still working.
Working time and time recording
The time recording (RCP) system remains the source of truth for working time settlement. A swipe event can feed both RCP and InnerWeb, and each system serves a different purpose: one for payroll and rostering, the other for safety and attendance. We do not recommend replacing one with the other.
At the specification stage for the access control system vendor, you describe which events and in what format should reach InnerWeb, so that the data needed for the evacuation list is available without changing the readers.
Order of implementation
Implementation starts with deciding who owns the swipe data in the plant, and ends with a test across three shifts.
- inventory of doors and readers where attendance is recorded,
- agreement with the access control vendor on the format of swipe events,
- test of the evacuation list on the day, afternoon and night shifts,
- rule for swiping out and anomaly control at the shift handover,
- evacuation drill with external contractors on separate tabs.
Video
Frequently asked questions
Do we need to replace the card readers?
No. InnerWeb does not replace readers. It integrates with the client's existing access control system, which supplies the swipe events.
Does InnerWeb replace the RCP system?
No. It complements the client's existing systems. RCP remains the source for working time settlement, while InnerWeb uses the events for safety and the evacuation list.
How often does the evacuation list refresh?
Every 13 seconds, divided into groups and with separate tabs for each external contractor.
Sources
Connect the evacuation list with your badge swipes
We will prepare a specification of events for your access control system vendor, without replacing the readers.
Let's talk