Security Center features supported by HID units - Security Center 5.8

Security Center Administrator Guide 5.8

series
Security Center 5.8
revised_modified
2020-08-17

This section lists the standard Security Center access control features that HID units support.

Readerless door

Readerless doors (doors that use an I/O module for a REX, door state, and door lock only) are supported, both when the unit is operating online and offline.

For readerless doors to work, the following is required:
  • The inputs of an HID VertX V1000 must be not used for this feature.
  • All inputs and outputs must belong to the same HID controller (one V2000 or one Edge).
NOTE: A readerless door does not support the buzzer feature.

Door control

Card and PIN
Card and PIN reader mode is supported if the installed reader supports it.

For card and PIN reader mode to work, all reader interfaces/inputs/outputs for a door must be controlled by the same HID unit (HID Edge, VertX V2000, or VertX V100 interface module).

PIN entry timeout
Supported as per door configuration.
Extended grant time
Supported as per door configuration.
Entry time (standard and extended)
Supported as per door configuration.
Door relock
The relock option on door closed is not supported. Only the delayed locking after the door opens is supported, and the maximum delay is 27 minutes.
Door held event and buzzer
Both the Door open too long event and the reader buzzer are supported as per door configuration.
Door forced event and buzzer
Both the Door forced open event and the reader buzzer are supported as per door configuration.
Request to exit (REX)
All REX handling behavior are supported as per door configuration.
Shunting
Reader shunting is not supported. Only inputs can be shunted.

People counting

People counting is supported only when all units used for this feature are connected to the same Access Manager. The moment a unit assigned to one of the perimeter doors of an area is offline, the feature is disabled for the entire area.

Security clearance

The concept of security clearance is not supported for areas controlled by HID units.

Elevator control

For elevator control to work, the following is required:
  • All interface modules used for elevator control (HID VertX V100, V200, and V300) must be assigned to the same VertX V1000. Reader, inputs and outputs must be assigned to the same V2000 (max. of 4 floors) or Edge (max. of 2 floors).
  • All units used for this feature must be assigned to the same Access Manager.
  • The reader interface, inputs, and outputs must be connected to the same HID controller (VertX V1000, V2000, or Edge). A maximum of 1 elevator cab reader can be assigned per HID controller (VertX V1000, V2000, or Edge).
NOTE: If you plan to offer both periods of controlled access and free access to your elevators, contact your representative of Genetec Inc. for a custom firmware to use with the units controlling elevators.

The use of HID VertX controllers (V1000 and V2000) for elevator control is subject to the following limitations:

  • A VertX controller should be dedicated to the control of a single elevator cab.
  • Once a VertX controller has been assigned to perform elevator control, it should only be used for that purpose. Door and zone control should not be mixed with elevator control, even when the unit has unused readers, inputs and outputs.
  • When elevator floors are operating under controlled access mode, schedules from different access rules applied to different floors are merged when the rules are granted to a same cardholder.
    Example: Bob is granted access to Floor-1 from 9 a.m. to 10 a.m. through access rule 1, and to Floor-2 from 10 a.m. to 11 a.m. through access rule 2. When Bob presents his card in the elevator, the VertX controller actually grants access to Robert from 9 a.m. to 11 a.m. on both floors.
  • Unlock schedules cannot be used on elevators controlled by HID units.

Elevator floor tracking

Floor tracking is only supported when the unit is online, and when all units used for this feature are assigned to the same Access Manager.

NOTE: Elevator floor tracking is not supported when the unit is offline because event reporting is unavailable. Events are not regenerated when the unit reconnects to Security Center.

Antipassback feature

The antipassback feature is supported both when the unit is operating online and offline.

For antipassback to work, the following is required:
  • Use either VertX V1000 (multiple areas and multiple doors per area) or VertX V2000 (area with a single door) controllers. HID Edge products are not supported.
  • All units used for antipassback must be assigned to the same Access Manager.
  • The interlock feature must be disabled. Interlock (including the lockdown and override functions) and antipassback are mutually exclusive; both features cannot be enabled for an area at the same time.
Antipassback works best once the access control system has been configured and the system is operational and relatively static. It is recommended to enable antipassback once the following entities have been properly configured in Security Center and are not expected to change on a daily basis:
  • Unit time zones
  • Doors and associated readers
  • Areas (groups of doors)
  • Elevators and associated floors (including unlocking schedules)
  • Cardholder groups
  • Schedules (including card and PIN schedules)
  • Access rules
The following section provides guidelines for configuring, enabling, and managing antipassback with HID VertX controllers (units):
  • You must use either the V1000 or V2000 for antipassback.
    • V2000: Antipassback is only supported for an area with a single door having both entry and exit readers.
    • V1000: Antipassback is supported for multiple areas, with each area supporting multiple doors with entry and exit readers. Limitation in the number of doors is based on the number of V100 modules installed.
  • Antipassback is not recommended with the Edge product line for the following reasons:
    • Only a single reader can be specified for either entry or exit (not both) while antipassback typically requires both entry and exit readers.
    • Peer-to-peer communication between Edge devices is not supported by Security Center.
  • An area with antipassback must be configured for readers wired to, and doors managed by, the same unit (V1000 or V2000) because:
    • Antipassback functions are handled by the unit (V1000 or V2000).
    • The Security Center does not support peer-to-peer communication between either VertX V1000 or V2000 devices.
  • Antipassback can be reset using the following methods:
    • A unit synchronization operation
    • An action (manually or with an event-to-action)
  • The following system behavior will reset a unit’s antipassback state:
    • Initial unit synchronization when the Security Center services are started or restarted.
    • Unit synchronization following the loss and recovery of a connection with the unit (V1000 or V2000).
    • Unit synchronization following certain configuration changes (see below for more details).
    • Manual synchronization of the unit through the Config Tool page.

Antipassback options

The following antipassback options are supported:
  • Soft antipassback (passback violation event generated and access is granted) is only supported when the unit is online. Soft antipassback is not supported when the unit is offline because event reporting is unavailable. Events are not regenerated when the unit reconnects to Security Center.
  • Hard antipassback (passback violation event generated and access is denied) is supported both when the unit is operating online and offline.
  • Strict antipassback (passback violation event is generated when a cardholder attempts to leave an area that they were never granted access to). With HID units, hard and strict antipassback are one and the same. There is no distinction between the two.
  • Antipassback on schedule is supported both when the unit is operating online and offline.
  • Antipassback on schedule is not supported with hard antipassback.
NOTE: The timed antipassback option is not supported.

Interlock feature

The interlock feature is supported both when the unit is operating online and offline.

For interlock to work, the following is required:
  • The antipassback feature must be disabled. Interlock (including the lockdown and override functions) and antipassback are mutually exclusive; both features cannot be enabled for an area at the same time.
  • The inputs of an HID VertX V1000 must be not used for this feature.
  • All perimeter doors of an interlocked area must be assigned to the same HID controller (one VertX V1000 or one V2000).
NOTE: If a perimeter door of an interlock is open, when an authorized cardholder accesses a second perimeter door of the same interlock, an Access granted event for the second door might be generated, even through the second door does not unlock.

Interlock options

The following interlock options are supported both when the unit is operating online and offline:
  • Lockdown
  • Override

First-person-in rule

First-person-in rule is not supported by HID units.

Two-person-in rule

Two-person rule is not supported by HID units.

Visitor escort rule

Visitor escort rule is not supported by HID units.

Event-to-actions

Event-to-action is supported when the unit is operating online and offline, with limitations.
Event-to-actions with Trigger output action
The Trigger output action type can be used in event-to-actions when the unit is online, and is partially supported when the unit is offline.
For the Trigger output action type to work, all units used for this feature must be assigned to the same Access Manager.
Event-to-actions with Silence buzzer or Sound buzzer actions
The Silence buzzer and Sound buzzer action types can be used in event-to-actions both when the unit is operating online and offline.
For these actions to work, all inputs and outputs must belong to the same HID controller (one VertX V1000, one V2000, or one Edge).
NOTE: The Action feature is not available with a readerless door.
Access granted events are not supported when the unit is offline
Event-to-actions based on the Access granted event do not work when the unit is disconnected from the Access Manager.

I/O Linking

The I/O linking feature is supported both when the unit is operating online and offline, with the following limitations.

  • The inputs of an HID VertX V1000 must be not be used for this feature.
  • All inputs and outputs must be controlled by the same HID controller.
  • Only the Trigger output action is supported when the unit is operating offline.