Choose Genetec zone types by where the logic executes

Bottom line: Choose the Genetec zone type from the component that must execute the logic and the operations required during an outage.

Source fact: documented behavior

The Differences between the types of zone topic is the primary reference for this Security Center 5.14 discussion.

The Security Center 5.14 table places hardware-zone I/O linking in the access control unit and lists online and offline unit operation. It places virtual-zone linking in Zone Manager and lists online unit operation. For I/O zones, linking executes in the selected master unit; the table lists online and offline operation and requires Synergis Softwire 10.2 or later. The I/O-zone entries for arming or disarming from Security Desk and through actions carry a separate condition: the master unit must be online.

What the source does not establish

The comparison does not make every command available offline or approve a physical safety design. Read the conditions for each required operation and the actual unit family. The documented execution location is a design input, not proof that an installed zone has passed an outage test.

Applicability questions

• Which component must continue evaluating the rule when a server or connection is unavailable?
• What unit types, Softwire versions and master-unit assignments are planned?
• Are the required operations local linking, remote arming, disarming or scheduled control?
• Which inputs, outputs and peer relationships must the selected type support?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends drawing the execution path before selecting a type. For a proposed rule linking field inputs to an output, name the input units, decision component, output units and operator control path.

1. Compare that drawing with the original table’s execution, unit, input/output and logical-operator rows. Review footnotes with the system integrator. Record each necessary condition next to the operation it constrains.
2. Separate continued rule execution from the ability to issue an operator command. Define the expected result for each required degraded state and obtain the facility owner’s approval for any physical test plan.
3. Use an approved test rig or controlled commissioning arrangement to exercise normal operation and the documented outage cases. Test local linking and the required operator commands as separate observations. Restore the approved configuration and investigate any result that differs from the design record.

Verification and evidence

Retain the rule requirement, chosen type, original table rows and footnotes, unit and master assignments, versions and execution-path drawing. Record the test conditions, input changes, observed outputs, command results and restoration evidence.

Have the system owner accept each required operation explicitly. Revisit the decision after moving logic, changing master units or altering dependencies. These are DSE design and verification recommendations; they do not guarantee offline continuity or replace qualified review of door, alarm or emergency behavior.

Official references

• Differences between the types of zone — Genetec; Security Center 5.14.

Source review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.