About zones - Security Center 5.9

Security Center Administrator Guide 5.9

Applies to
Security Center 5.9
Last updated
2022-09-12
Content type
Guides > Administrator guides
Language
English (United States)
Product
Security Center
Version
5.9

A zone is a type of entity that monitors a set of inputs and triggers events based on their combined states. These events can be used to control output relays.

The concept of a zone is borrowed from the world of alarm panels, where electric inputs are associated with zones to trigger specific alarms. In Security Center, electrical inputs are associated with zones to trigger events. Using event-to-actions, these events can be used to not only trigger outputs, but also to trigger alarms, send emails, start camera recordings, and so on.
Tip: You can also define custom events to correspond to each of the special input combinations.

A zone can be armed (triggers activated), or disarmed (triggers deactivated) using a key switch, a software command, or on a schedule. A zone can be armed by software (using an action command or according to a schedule), or by hardware (for units that support this feature).

I/O linking

I/O linking is the control of specific output relays based on the combined result of a specific set of electric inputs. Each input can be connected to a specific monitoring device, such as a motion sensor, a smoke detector, a door or window contact, and so on.

For example, if a window shatters, the glass break sensor on a window connected to an input on a unit, can be linked to an output that triggers a buzzer.
CAUTION:
On HID VertX units, some inputs, such as AC Fail and Bat Fail, must be configured for something other than their initial purpose (leave the checkboxes empty) before they can be used for I/O linking. However, other inputs, such as Door Monitor, can only be used for their designated purpose. If you use a specific purpose input as general purpose, your configuration will not work. Do not exceed 20 inputs per zone with HID VertX units. Exceeding this limit may lead to unit synchronization problems.

Zone states

Zone states are determined by a combination (AND/OR) of inputs associated with the zone.

The following zone states are available:
Normal
When the combination of inputs yields a zero (0).
Active
When the combination of inputs yields a one (1).
Trouble
Requires to have at least one supervised input. The zone is in the Trouble state when at least one of the input is in the Trouble state. The Trouble state supersedes all other states.

Hardware zones

A hardware zone is a zone entity in which the I/O linking is executed by a single access control unit. A hardware zone works independently of the Access Manager, and consequently, cannot be armed or disarmed from Security Desk.

Hardware zones are recommended when quick responses and offline operations are crucial for your security system. The access control unit controlling the zone must not be operated in server mode. Once the unit is configured in Security Center, it must be able to act on its own without being connected to, or controlled by Security Center.

Hardware zones can be armed using a key switch (input), or on schedules.

Virtual zones

A virtual zone is a zone entity where the I/O linking is done by software. The input and output devices can belong to different units of different types. A virtual zone is controlled by the Zone Manager and only works when all the units are online. It can be armed and disarmed from Security Desk.

Virtual zones are recommended when flexibility is required, and when access control units are not available.

I/O zones

An I/O zone is a zone entity in which the I/O linking can be spread across multiple Synergis™ units, while one unit acts as the master unit. All Synergis™ units involved in an I/O zone must be managed by the same Access Manager. The I/O zone works independently of the Access Manager, but ceases to function if the master unit is down. An I/O zone can be armed and disarmed from Security Desk as long as the master unit is online.

I/O zones are recommended when quick responses, offline operation, and I/O linking across multiple units are required.