Configuring In / Out Reports for Brivo Mercury Solutions

Richard Crowder Updated by Richard Crowder

Configuring In / Out Reports for Brivo Mercury Solutions

Introduction

Brivo Access, In / Out Report is specific to knowing if a User is in a space or out. Doors or readers can be designated as In or out and the report is generated based on the last door or reader that the user accessed. To configure a proper In / Out report, most systems will need to be installed with In (ingress) readers and Out (egress) readers. Brivo Access supports In and Out Reporting for both Single Reader Door Nodes and Multi-Drop configurations. In the Single Reader Node, the setup for In / Out Reporting is identical to how In / Out Reporting is configured for Brivo ACS panels. If using Multi-Drop for multiple OSDP readers, In / Out Reporting requires a configuration using Anti-Passback. The configuration of both is outlined below.

Single Reader Node Configuration

In a Single Reader Node configuration (Wiegand or Single OSDP), for In and Out to occur, readers or doors will need to be designated as In or Out. In some configurations one door node may be considered the In Node and the other will be the Out Node. The Out node will be hardwired to the In Node in order to operate a single physical door. In some cases, a designated Entry door can be defined and then a designated Exit door can be defined, but not restricting the movement of individuals. The different Single Node configurations are demonstrated below

Configuration A: Single Entry with no Exit

In this configuration, you would only be concerned about the entry of individuals per day. This could be used for a simple site access report. Example: User A entered at this time. There is no need to setup an out reader because you are not concerned who has left the site in a given day.

Configuration B: Dedicated Entry Node and Exit Node Controlling One Door

In this configuration, you typically have your Entry Node as the primary controlling node. There are multiple ways to wire this configuration as shown above. It will all depend on the type of lock and the number of relays that are available on the panel. Note that this is not available on the SDC or ACS100. In the first example given, the Entry node controls the door lock relay. The second or Exit Node is controlling the Rex on the Entry Node. A modification of this can use the Door Lock Relay being tied to an Auxiliary Input as well as a REX device so that only one device triggers the Rex input and does not interfere with the other. It is possible to put these in series, but another issue can arise when trying to monitor the input devices.

Configuration C: Dedicated Entry Node and Exit Node Controlling Separate Doors

Dual Reader Node Configuration (OSDP - Multi-Drop)

When Using Multi-Drop, the Alternate Reader will not be differentiated by the panel from the Primary Reader and requires Anti-Passback to be set. Anti-Passback can be set for "Soft" with a reset time of 1 minute, but would enact Anti-Passback rules for that one minute, unless Immune to Anti-Passback is assigned to the User Group.

If the Primary is set to In, any reader that is used as the Alternate for Anti-Passback will be automatically used as the Out reader

The alternate reader will automatically be reported as the door it is configured to unless the reader is assigned as the alternate reader for another Door in the AntiPassback Settings. 

How did we do?

Configuring Multiple OSDP Readers per Node

Contact