Building a specification & want to specify Urmet? Use this article to specify our IP Access Control System 'IPassan', and it's related system products
Contents:
System
Products
System Overview
The main purpose of the access control system is to permit authorised access to users such as residents, building management, visitors and restrict unauthorised access. The access control system shall be Secured by Design accredited using UL293 certified products.
The access control system shall be an IP cloud-based online system. Door controllers shall be capable of being connected to a dedicated LAN or VLAN (shared / managed network). If there is no IP network available, the system shall be capable of using a RS485 network. The system shall be capable using IP and RS485 in the same network. In the event of disconnection between a door controller and the network, the access control system shall continue to operate using the last access profiles configured. Once the connection has been re-established events shall be transferred to the cloud/server automatically. The access control system shall not be reliant on the cloud/server to operate.
The access control system shall support the following installation:
- IP (Ethernet - Fixed IP or DHCP)
- RS485
- Hybrid (mix of Ethernet and RS485)
The access control system shall be set-up via the management software which can be installed on a PC or via the cloud to enable remote access.
The access control system shall support the following management: -
- Offline – for applications where the site is set up on a laptop for example and then left to run standalone i.e., without a PC or laptop permanently connected. All information from the site (events etc.) can be interrogated later when a PC or laptop is reconnected.
- Server – software for applications where a PC will be permanently left connected to the site. The software will be permanently running e.g., where a site has a Concierge or management office onsite. System door controllers shall not be reliant on the server.
- Online (Cloud) – for applications where remote administration is required using the cloud. Internet connection required. System door controllers shall not be reliant on the cloud.
- Custom – for complex applications i.e., multiple PCs across a network for example where the system database can be managed from one PC and the communications from another PC.
Performance Overview
System type: Access Control
System manufacturer: Urmet
System name: IPassan
System technology: IP, 2 wire
Communication network: Ethernet TCP/IP (LAN/VLAN), RS485
Online: cloud
Offline: server (software) or standalone
Architecture: client / cerver
Accreditation: Secured by Design
Certification: UL293
Application: multi-dwelling residential applications that have a high number of controlled access points (e.g., doors, gates & lifts)
Integrations: Onvif, Bluetooth, NFC, lifts, ANPR, visitor booking, door entry
Encryption protocols: OSDP, ANSII, OSS, AES, 13.56MHz, Mifare® Classic, Mifare® Plus and DESFire, Bluetooth Low Energy (BLE), 868MHz
Configuration: Automatic controller discovery
Credential capacity: up to 100,000 credentials per site
Door/Site capacity: unlimited number of doors per site / 384 doors per network
Lift management capacity: up to 110 floors
Encryption: multi reader and credential technology
Protection: Anti-passback
Event capacity: unlimited (cloud)
Local event capacity: 20,000 events per controller
Notifications: Email or SMS alert messages
Firmware upgrades: over the network
Products
Select the products that you require for the specification.
Door Controllers
Door Controller Overview
Door controllers shall be UL293 certified Urmet IPassan base controller ref. 1104/921. The base controller shall be capable of controlling 4 doors (readers). The base controller shall be capable of being expanded to a 6 door controller using a 2 door expansion card.
Door controllers shall be capable of being networked via the TCP/IP network or via the RS485 BUS. Door controllers shall use a 2 wire connection to the door reader ensuring secure bi directional data communication between controller and reader with end to end encryption. Non encrypted communication such as Wiegand shall not be acceptable. The door controller firmware shall be capable of being updated remotely. Door controllers shall allow the connection of additional input / output relay base expanders via RS485. Door controllers shall be powered by a 12VDC PSU with battery back up facility.
Data and configuration shall be stored locally in case of a remote server crash or network failure. The Door controller shall not be reliant on a server or cloud connection to operate. All events shall be stored locally in the door controller and automatically transferred to the server or cloud upon reconnection. The access control system shall have embedded intelligence allowing the firmware of the door controller and connected readers to be updated by the software remotely.
Door Controller Performance Overview
Type: 4 door base controller
Part number: 1104/921
System: IPassan
Technology: IP, 2 wire
Power: 12VDC
Network: Ethernet (TCP/IP), RS485
Cabling: Cat5e/Beldon
Encryption protocols: (OSDP, ANSII, OSS) AES, 13.56MHz, Mifare® Classic, Mifare® Plus and DESFire, Bluetooth Low Energy (BLE), 868MHz
Accreditation: Secured by Design
Certification: UL293
Operating voltage: 12VDC – up to 1A with 6 readers
Reader connection: 2 wire
Reader outputs: 12VDC 80mA output per reader
Door relays: 4 48V 2A relays
RTE input: Protected by an optocoupler
Door contact input: EOL management
Tamper: (x2 Normally off) – 1 for the cover of the controller + 1 for the housing
LED status: Indicators showing the status of all readers and relays
Fixing: Wall or DIN mounted
Dimensions: L200 mm x W90 mm x H34 mm (210 mm x 145 mm x 65 mm with cover)
Readers
Readers Overview
The access control system shall be capable of offering UL293 certified wall mount and panel mount readers. The Secured by Design accreditation must cover the actual location of a wall mounted reader and visitor entry panel mounted reader e.g. within adjacent wall or other structurally sound fixing.
The access control readers shall use a 2 wire connection ensuring secure bi directional data communication between controller and reader with end to end encryption. The reader firmware shall be capable of being updated remotely.
Access control reader only doors shall be wall mounted readers using 2 wire technology. The readers shall have a IP65 and IK10 rating. Where the access control system is used in conjunction with a door entry system the entry panel shall be fitted with a 2-wire panel mount reader. Readers shall have LED signalling and audible tone to indicate valid or non-valid credentials.
The access control readers shall be compatible with the following encryption formats, 13.56 MHz (Mifare® Classic, Mifare® Plus and DESFire) + Bluetooth Low Energy (BLE)
Where required a reader keypad combing a reader and a coded access keypad which can be programmed to validate credential and code or credential or code.
RF readers shall use 868Mhz frequency and shall be used where required for carpark barriers/shutters for entry/exit. It’s suggested that when using the RF readers for vehicle access that and induction loop be installed for ingress and egress so that a vehicle has to be on the induction loop for the remote activation to work, therefore maintaining security of the building/car park.
Readers Performance Overview
Type: Wall mounted, panel mounted, RF (long range)
Part number: 1104/993 (P80), 1104/992 (P40), 1104/994 (PK80), 1104/953/951 (panel mount), 1104/941 (RF)
System: IPassan
Technology: 2 wire
Power: By controller
Cabling: Cat5 STP (100M from controller)
Encryption protocols: 13.56MHz, Mifare® Classic, Mifare® Plus and DESFire, Bluetooth Low Energy (BLE), 868MHz
Accreditation: Secured by Design (P80 reader, 2Smart panel mount reader)
Certification: UL293 (P80 reader, 2Smart panel mount reader)
Reader connection: 2 wire
Fixing: Wall or panel mounted
Ingress protection: IP65 (P series range)
Impact rating: IK10 (P series range)
Dimensions: Dependent on type of reader
Credentials
Credentials Overview
The access control system shall be capable of managing key ring type tokens (fobs), combined RF (radio frequency long range remote) tokens, cards and Bluetooth (virtual) credentials.
Physical credentials, such as tokens (fobs) and cards shall be compatible with 13.56Mhz Mifare® Plus 128 bit with AES encryption and DESFire to prevent cloning. Bluetooth (virtual) credentials shall utilise an anti-replay mode for anti-cloning functionality, which prevents a third party from intercepting and copying the communication between the App and the Bluetooth reader, meaning that the Bluetooth Credential cannot be cloned.
Key ring type tokens (fobs) shall be IP68 and impact resistant to IK08, they shall have a robust metal key ring holder and have a unique engraved ID number. Tokens shall be available in 5 colours.
Cards (ISO) shall be credit card size and have a unique engraved ID number. Cards shall be capable of being customised with a logo and/or photo. Cards shall be capable of cashless vending.
Combined RF long range (radio frequency remote) tokens shall have 4 buttons and combine 13.36Mhz for proximity and 868Mhz for remote activation they shall have a robust metal key ring holder and have a unique engraved ID number.
Bluetooth (virtual) credentials shall offer three levels of operation:
- proximity access for one day (visitor for example)
- permanent proximity access
- permanent long range and proximity access
Credentials Performance Overview
Type: Key ring token, combined RF token, card, Bluetooth credential
Part number: 1356/11 (tokens/fobs), 1356/CARDPLUS, 1104/71 (RF remote), BLECRD01 (Bluetooth virtual credential)
System: IPassan
Encryption protocols: 13.56MHz, Mifare® Classic, Mifare® Plus and DESFire, Bluetooth Low Energy (BLE), 868MHz
Ingress protection: IP68 (1356/11, 1104/71)
Impact rating: IK08 (1356/11, 1104/71)
Dimensions: Token/fob (1356/11) H49mm x W36mm x D7mm, RF long range remote (1104/71) H79mm x W38mm x D12mm
Management Software
Management Software Overview
The access control system shall not rely on software installed locally on the operators PC. The software shall be capable of being installed on a server allowing system updates to software, smart controllers, expanders and readers.
The access control management software shall use a web browser and be intuitive and easy to use.
Using the management software, it shall be possible to:
- Manage access rights and doors
- IP Search to find all smart controllers on the network
- Access levels shall include administrators, managers, users and guest rights
- It shall be possible for an extra level of security to be achieved via a specific fob on the encoder. In this case, the login and password shall not be sufficient to log on to the system and make modifications. Only the owner of the fob has the access rights to open the software and its associated sites
The access control management software shall have operator authorisation to:
- Assign access rights to credential holders
- Create groups
- Associate doors
- Calendar to schedule days, times and holidays
- Anti-passback preventing a credential holder from passing his credential back to a second person to enter the same controller area, for example a car park.
- Live events automatically keeping an event log, producing management reports (track card usage and door activity)
- Check the status of the controllers, readers or any other hardware
- Control doors, floors or inputs manually
- Lift management grants residents’ access to designated floors. If the resident has access to the lift, then they also present a credential to the reader inside the lift before any of the restricted floor buttons are available
- Interface with Urmet door entry system to record and log resident/visitor events i.e. time and date of visitor call from entry panel, lock release from apartment station etc.
- Interface with Urmet door entry system for lift management with floor destination for visitors
Thresholds (counting)
The access control system shall be capable of managing thresholds for activations or events. Thresholds shall be definable for access control, door entry integrations and other devices such as self-resetting emergency exit systems e.g. if a button is pressed >20 times during a 24hr period an email is sent to the building management company.
Lift management
The access control system shall be capable of interfacing with the lift manufacturer either via I/O (input output) modules or software (COP or DOP). For software integration the access control system shall offer an API for integration. The access control system shall be capable of interfacing with an Urmet door entry / intercom system.
Dependent on the logic capability of the lift, the lift control via I/O (input output modules / software / interfaces shall provide the following:
Resident
- Resident presents credentials to reader to call lift
- Resident presents credentials to reader to call lift, allowing access rights to all or pre-defined floors
- For applications where a combined reader/keypad is used, unique codes can be used to allow access rights to all or pre-defined floors
- Management software can call lift or send lift to any floor
- Resident calls lift to their floor using the apartment station
- Resident can send lift to egress floor using the apartment station
Visitor (when interfaced with Urmet door entry systems)
- Visitor calls resident, resident releases door lock via the apartment station, lift called to ingress floor, lift provides access to residents’ floor
In the event of disconnection between a smart controller and the cloud server or internet failure, the lift access control shall continue to operate using the last access profiles configured. Once the connection has been re-established the events shall be synchronised automatically.
CCTV integration
Using the management software, it shall be possible to add an NVR, link a door with a camera and provide access to video recording from an event. The management software shall be compatible with ONVIF. The management software will be compatible with third party ANPR cameras.
Third party integration
The access control system shall have an API available to allow for third party integrations.
Door entry integration
The access control system shall be capable of being fully integrated with the door entry system either by using an interface (hardware) or high-level interface (software).
2Smart integration (2 wire) using the UL293 certified EP-2SMART-SS 2Voice 2 wire video door entry panel with built in 2 wire reader it shall be possible to integrate the door entry system with the access control system. The EP-2SMART-SS 2Voice 2 wire video door entry panel with built in 2 wire reader connects to the UL293 certified IPassan 1104/921 access control system controller.
Hardware interface (2 wire) using the management software, it shall be possible to add a door entry interface or door entry panel (compatible door entry systems are Urmet 2Voice). The Interface is an advanced interface designed to collect data travelling between an Urmet 2Voice entry panel and the called apartments. This device enables extensive monitoring of the door entry system such as event logging and lift management.
Software interface (IP) using the management software, it shall be possible to fully integrate the door entry system (compatible with Urmet IPerCom door IP door entry system). Standard integration - designed to collect data travelling between an Urmet IPerCom entry panel and the called apartments allowing event logging of the door entry system. Advanced integration - lift management shall be offered via an IPassan activation code 1104/978.