Peripass access integrations
When do you need this
When you want to grant or revoke physical access for your visitors.
Main idea
For transports:
When a transport is called off, they are granted access. The access granted depends on the type of flow. The drivers receives a text message for call-off including a unique pincode.
Driver can use his personal pin when entering the site. Peripass is informed as soon as a driver accessed your premises. This is visualised on your dispatch dashboard.
PIN for the exit barrier is only activated when (un)loading is finished, prevent the driver from leaving your premises before all paperwork is finished.
When the driver leaves your site, Peripass is informed once more.
For office visitors and contractors:
When an office visitor or contractor registers at the kiosk, a badge is dispensed and activated.
Office visitors & contractors can use the badge to access the site.
During check-out visitors inactivate and dispose the badge.
2 ways to integrate
PIN-point
What is this?
The Peripass PIN-Point verifies the PIN via the Cloud and opens any barrier, speedgate or turnstile from the Cloud. This without the need to integrate with your existing infrastructure.
Implementation lead time
1 week.
How does it work
A PIN-point is a plug and play box that is installed next to your barrier.
The PIN-point only needs power supply and connects via 4G to the Peripass Cloud.
Advanced integrations
What is this?
An integration between Peripass and your existing Access Control System allows to automate the integration of PIN-code and badges from Peripass. All existing equipment (PIN-pads, badge readers) can be used.
Implementation lead time
6-9 months.
Some of our standard integrations
How to decide the best solution for your situation
PIN-Point | advanced integration | |
|---|---|---|
Direct cost of implementation by Peripass | / | Supported ACS brand: starting from € 1.500 one-off. New ACS brand: starting from € 13.520 (*) one-off. |
Implementation effort | / | IT infrastructure team and 3rd party support (ACS provider). |
Physical location | Works with a 4/5G router. | Should always be accessible from the local network. |
Badge support for contractors & visitors | No | Yes |
Evacuation list | Available in Peripass for all visitors registered with Peripass. | Available in Peripass and in Access Control System. |
Guidelines for granting access
Always grant visitors access on check-in, not sooner:
Creating too many pincodes could overload the ACS system or could result in unwanted side effects as ACS systems are not designed for this type of large volumes.
Example: Imagine a site with 100 unique daily visitors. If all of them are invited 6 months in advance, this will create 18.000 visitors with a unique pincode in the system. When your pincode contains 4 numbers, there are only 10.000 combinations possible.
Only following exceptions are allowed:
Grant visitors access on the morning of their planned their arrival
Only when visitors for this profile are limited to 50 unique visitors per month AND when you can reach the visitor up-front (e.g. only for recurring transports like waste recycling or offices visitors or contractors).
Announce in the first communication that they will receive a PIN-code via mail on the day of their visit.
Grant access early in the morning (e.g. at 2:00).
At that moment, send an email to the visitor with their PIN-Code.
Grant recurring visitors a pincode that is changing every 30 days
Only when there are max 10 visitors for this type of profile (e.g. a single visitor for a waste company per site)
Always communicate the PIN-code through a text message.
It is not possible to show a PIN-code on the final screen during a registration, as this way it can be seen by other drivers and there is no way for a driver to re-read the number when he is trying to enter the yard.
Ticket printers need much more maintenance (paper stock and feed issues), cleanup of the yard, tickets can get lost
There is one exception: use ticket printers in case it is crucial for the process that the pin code is always and immediately received by the driver
E.g. fifo waiting queue that blocks the entrance
Reason: in 1-3% of the cases a text message will not be received by the driver.
Won’t do / limitations
It is not possible to combine 2 advanced integrations (ACS integrations) on a single site. In other words: a single Local Action Worker can only integrate with one Access Control System.
It is currently not possible to combine a PIN-Point and an advanced integration on a single site. The product team is gathering information about this, so please contact them if you would need this.