Creating an alert
Data property the same as does an analytic proxy extension and analytic binding, which you can technically configure with a tag
or tag group; however, the intention of an alert is to configure the Data property to reference an algorithm, which has some fault detection logic that returns a Boolean value. The Alert's Poller property configures how often the Alert automatically processes the configured algorithm. This updates the applicable properties
on the Alert component. When the result of processing the algorithm returns a true value, an alert condition exists. The Analytic Alert Manager view on the Alerts component summarizes the current state of all alerts. The Alert Nodes View on an individual alert provides the details for each alert.
You may also configure an alert to generate an alarm record,
- Double-click .The Analytic Alert Manager opens.
- Do one of the following:
- To create a new alert, click New.
- To modify an existing alert, select the alert and click Edit or double-click the alert in the row.
The New or Edit window opens.
Pay special attention to these properties:
Datadefines the algorithm that returns true or false. When true, the alert exists; when false, no alert exists.Rootsdefines where to collecting data for the alert. This alert runs against all devices under the Drivers/BacnetNetwork/Global folder.Node Filterreduces the number of nodes to search.n:devicelimits alerts to devices. This is an appropriate place to use a NEQL predicate.Alert Modeprovides two settings.Alert after, configures when to generate the alert. The second drop-down list identifies how many of what to use to generate the alert.Occurrencesgenerates an alert after the selected number of the same event occurs.Seconds,MinutesandHoursdefine how much continuous time must elapse where the algorithm result is true for an alert to be generated. This value is part of the total cost calculation.Costassociates a currency value with each alert occurrence.Pollerdefines how frequently to run the alert.Alarmcontrols alarm generation. The default isfalse(no alarm generation).
If you are testing, consider creating an Analytics Smart Alarm Class and send all framework alarms to this class as an easy way to differentiate between alarms coming from a standard alarms extension and the alarms coming from the framework.
The rest of the properties are described in the Niagara Analytics Framework Reference.
- Configure properties and click OK.
- To complete the configuration, right-click the AnalyticService and click .This step is required any time you create a new or edit an existing alert.
- After creating the alert, double-click it in the Nav tree.The Alert Nodes View opens.
This view displays the current state of all points monitored by the alert.
- If the view is empty, right-click the AnalyticService and click If you still do not see the points in the table, click Refresh at the bottom of the window.