Configuring Custom Event Policies

Event policies can be configured to trigger events and alarms based on one or more conditions, such as the event type, the source device, device type, location, time of occurrence, or other factors.

·         If an event policy includes more than one condition, all the conditions must match for the event to be triggered.

·         If multiple events apply to an event occurrence, the most specific event policy is executed. Since only one event policy can be triggered for any event, only the most specific event is used. To determine the most specific event, the following criteria are applied in decreasing order (the criteria at the top of the list are given greater importance):

o       Log code

o       Log code category

o       Device instance

o       Device group

o       Partition

o        Hierarchical location (Building, Area, etc.)

o       Device type

o       Time schedule

o        Invert time schedule (That is, “Not in” time schedule)

Examples

·         If one event policy is based on a log code (such as Door Forced Open) and a second event policy uses the same log code in combination with other criteria (such as Time schedule), then the second event policy is selected.

·         If one event policy is based on a device type, and a second is based on a device instance, then the device instance event prevails since it is higher in the list of criteria.

·         If two event policies are based on the same time schedule, but the first event defines During time schedule and the second event defines Not during time schedule, the first one event policy is used since During time schedule is higher in the list.

·         If one event policy is based on a log code and a second policy is based on a collection of log codes and a location, all events in that location will use the second policy. Events from other locations will use the first policy.

 

See also:

Modifying Default Event Policies

Configuring Events and Alarms