Configure classic events

You can use the Classic Event subsystem to set up the detection of events and associate actions with those events. At a basic level, anything that can be determined by looking at historical or system data can be used as an event. The Classic Event subsystem stores data to SQL Server.

Important: The Classic Event subsystem is not a real-time system; rather, it operates on historical data. For real-time alarming, use an application such as the InTouch HMI.

When setting up an event, you must provide the following information:

• The criteria for the event. For example, the value of an analog tag being equal to 1500 could be an event. Also, the system clock on the AVEVA Historian computer reaching 9:30 a.m. on Monday morning could be an event.

• How often you want the Classic Event subsystem to check if an event occurred. This is called event detection.

• Whether or not you want information about the event detection saved to the database.

• Whether or not you want to execute an action as a result of a successful event detection and the type of action. For example, send an e-mail message.

The configuration information for the detection and action for a particular event must be given a unique name, which is stored as an event tag.

The Historian also supports the storage of alarms and events generated through external sources such as Application Server to history blocks.