Plan system configuration

Both the Niagara station and Mercury panel(s) require configuration. Many options are available. Naming conventions need to be considered and simple system documentation designed.

Panel and station configuration

Implementing the Mercury driver involves coordinating the Mercury panel configuration with the Niagara station configuration of the Mercury driver. Included is any integration with other station control logic. For example, if an input type Mercury proxy point representing an access area transition is set to “true” during an unscheduled (off) time, you may want to override a zone’s air handler (HVAC) and lighting control points to an occupied (on) state during this period.

The way you configure the Mercury driver can affect system access of both:

a NiagaraAX station user, providing Mercury access control information
a Mercury access control system user, providing NiagaraAX control system information and related alarms

Best practices

Before you begin, make a list of the configuration you will need, including:

The number of Mercury panels and portals (this will give you an idea of how long device discovery might take)
What Niagara device alarms to report to the Mercury security system
Any other device control and reporting requirements (for example, you could use portal status to control Niagara devices, or even use the NiagaraAX station to connect a Mercury input with a Mercury output)
Design naming conventions that clearly describe connections and which points are virtual ones.
Write down the configuration in the form of a diagram.