Who these recommendations are for
The recommendations are addressed to the security chief, the head of technical services and the integrator who prepares an access control concept for a power plant or heating plant. They assume the plant already has an access control system with readers at gates and doors, and the question is how to complement it without replacing the hardware.
InnerWeb is a software producer, not a reader manufacturer. It does not sell access cards and does not replace existing readers. It integrates with the client's access control system and connects its events with qualifications, permits, attendance and time recording. This division is the starting point for everything else.
Recommendation 1: the gate level is the permission verdict
At the gate one thing is decided: may this person be on the plant. The security screen gives a verdict after scanning a QR badge or an RFID card, based on training, qualification for hazardous work, an open work permit and an active account. The scan records the entry, and there is no separate button to let someone in.
Reasoning: whoever judges the verdict at the gate has the full picture of permissions. Do not require the lock reader to know whether a training is valid. If the operator prefers to leave the access reader unchanged, the badge event is passed to the system by webhook, and the permission rules are calculated by the software.
Sample time parameters to agree in the specification
Recommendation 2: the building level is a trace of access control events
Entering a building is the classic task of a reader at a door. InnerWeb receives the card event from the access control system by webhook (POST, authentication with a token with a limited validity period, renewed automatically by the integration). The event carries the reader timestamp, the location of the reading and the person's data with the active card number.
Reasoning: the plant does not need to install a second layer of readers. The integration specification for the access control vendor assumes that the access control system sends events in real time, with the reader event time, the direction (entry or exit) and the event identifier. This way the trace in the building matches what the reader recorded.
Recommendation 3: the floor level is location, not a reader
In a multi-level boiler house it does not pay to put a reader on every catwalk. The floor is indicated by the position from BLE transmitters. The heartbeat carries signals from the transmitters received, the signal strength, the battery and the status, and from these the system calculates the position. A 3D position requires readings from at least 5 transmitters.
Reasoning: location does not require any gesture from the employee, so it works even when someone forgets to tap the card at the platform door. The reader says that someone passed, the transmitters say where they are now.
Recommendation 4: one evacuation list from three sources
The evacuation list is built from QR scans at the gate, refreshes every 13 seconds and divides people into six groups: guests, couriers, suppliers, plant employees, external companies and uncertain. Trade-offs are resolved in favor of showing too many people rather than too few.
Reasoning: during an evacuation it is better to search for a person who is already gone than not to search for one who is still there. Access control taps and floor positions from location feed the same list, not separate reports that security would have to reconcile by hand.
Recommendation 5: do not duplicate registers
If access control records a tap in one place and working time records in another, the hours will drift apart after the first month. Gate scans can feed working time records (mRCP) with daily, monthly and annual views, exception queues, a timesheet in PDF and a reminder by phone about an unscanned exit. The module is disabled by default and is enabled by the administrator.
Reasoning: the decision which register is the master belongs to the plant, not to the vendor. It is worth writing it into the procedure before the integration starts.
Recommendation 6: entry and exit pairing rules are set in the specification
The rules for pairing entries and exits and for rejecting duplicates are set in the specification with the access control vendor, for example an entry-exit pair window of up to 13 hours and rejection of duplicates within an interval of less than 180 seconds. In one installation's measurement there were about 2,100 taps per day.
Reasoning: without clear rules the count of people on site drifts apart after a few days. We recommend writing the event direction into the specification, and for older readers without direction, agreeing with the access control vendor how it will be determined.
Recommendation 7: define what is not the task of InnerWeb
Locks, readers, access cards and their encryption remain with the access control vendor. InnerWeb adds to them the permission verdict, the register, the list of people on site and the location. Recording this division in the request for offer saves weeks of negotiation with two vendors, each of whom assumes the other will handle the topic.
Video
Frequently asked questions
Do the existing readers have to be replaced?
No. InnerWeb does not produce readers and does not replace them. It receives tap events from the client's access control system by webhook and connects them with permissions.
How do you tell the floor apart without a reader?
From the position calculated from BLE transmitters. A 3D position requires readings from at least 5 transmitters, so the placement is designed separately for each floor.
What about taps without direction?
The rules for pairing entries and exits and for rejecting duplicates are set in the specification with the access control vendor, for example a window of up to 13 hours and duplicates under 180 seconds.
Let's split the three levels for your plant
We will go through the gate, buildings and floors together and show what stays in access control and what the software takes over.
Let's talk