Preconditions: what must be clear before the rollout starts
The evacuation list answers one question: who is physically on the plant site now and where to look for them. It is built from QR scans at the gate. Every rollout decision follows from this rule. If no scan takes place, the person is not visible, and if no exit scan takes place, the person stays on the list for longer than they are in the plant.
Before the first meeting, IT and security should answer five questions: how many entrances the office block has, which of them pass the gate with scan control, who issues QR codes to the office, where to place the scanner at the office block entrance, and who is responsible for its operation. Without these answers the list does not contain office employees, and nobody notices until the day of the exercise.
Rollout steps in the recommended order
The order matters, because some steps depend on the results of earlier ones. The whole can be carried out in stages, starting with one building.
Step 1: inventory of entrances
Security walks around the office block and lists all doors used by employees: main, car park, side and the one from the laboratory side. For each one it records whether it leads through the plant gate. The results of the inventory decide how many scanners are needed.
Step 2: choosing the scan point
There are two approaches. The first: the office scans the code at the plant gate, like everyone else. The second: the office scans the code at its own office block entrance. The choice depends on the layout of the site and on whether the office block has an entrance outside the gate. Whichever variant is chosen, each employee must have one scan point and know which one it is.
Step 3: delivering QR codes
Office employees need a code carrier: a printout, a badge or a code on the phone. The plant decides who is responsible for issuing and renewing it. In this step IT establishes how an employee from the office block lands in the plant employees tab of the evacuation list, and not in the group of guests or external companies.
Step 4: pilot on one floor
Before the scan goes live across the whole office block, it is worth running it on one floor or in one department for two weeks. The pilot shows whether people carry their codes, whether they leave them at home, and how often an entry scan occurs without an exit scan.
Step 5: review of the Uncertain tab
After a week of operation security reviews the Uncertain tab. A person whom the gate register still treats as present does not disappear from the evacuation list, but moves to this tab with a reason, for example when the last entry is older than 12 hours or when the exit scan was refused. The conclusions of the review show which entrances need an exit scanner.
Time parameters of the evacuation list
Time parameters you need to know
The automat closing stays runs every 3 hours, and the default maximum stay without an exit scan is 12 hours. For an office that works fixed hours, this means that an exit scan forgotten in the evening will leave the main list only after a few hours, and until then the person may appear as present or in the Uncertain tab.
The list divides people into six groups in a fixed order: guests, couriers, suppliers, plant employees, external contractors and the Uncertain tab. The rollout team should read this order aloud to security, because floor coordinators in the office block will look for their people in the fourth group, not in the first.
Implementation pitfalls
The first pitfall: the scanner at the office block entrance has no network or power, so the scans do not arrive. The second: codes are issued, but some employees enter through side doors that nobody inventoried. The third: employees treat the scan as a formality and scan the code for a colleague. The fourth: nobody reviewed the Uncertain tab, so the list looks complete when it is out of date.
The fifth pitfall concerns expectations: the evacuation list does not replace the plant evacuation procedure. The printout is one page per group, so the incident commander can hand out sheets to coordinators at the assembly point. The evacuation procedure, the assembly points and the duties of coordinators remain the plant's document.
Integrations and the limits of the system
InnerWeb is an independent system that complements the client's existing systems: access control, time and attendance, HR and ERP. It does not manufacture access control readers and does not replace them. If the plant has its own access control system at the office block entrance, the rollout team agrees with that system's supplier whether, and in what form, its events may reach InnerWeb. This is a point to agree, not a standard setting, so it must not be assumed to work on its own.
Video
Frequently asked questions
Where should office block staff scan the QR code?
The plant chooses one place: the plant gate or the office block entrance. It matters that every employee knows that place and scans both entry and exit there.
Which group of the list does an office block employee land in?
They should land in the plant employees tab, the fourth of six groups. IT checks this in the pilot before extending the scans to the whole building.
Does InnerWeb replace the access control system in the office block?
No. InnerWeb complements the plant's existing systems and does not manufacture access control readers. Passing events from an existing system is agreed with its supplier.
Plan the scans for your office block
We will go through the entrances of your office block with IT and security, the scan point and the order of the evacuation list rollout.
Let's talk