7.5 Generating Events
The Event section (section 4 of the analysis form) controls whether the analysis creates an event each time it fires. Event generation is disabled by default.
7.5.1 Enabling Event Generation
To enable event generation, check the Generate checkbox in the Event section header. When enabled, the event fields become active and an Event Attribute column appears in the Output Attributes table in section 3.
When event generation is disabled, the section displays "Event generation is not enabled" and no events are produced.
7.5.2 Event Fields
Once event generation is enabled, the following fields must be configured to define the event's structure, severity, and delivery policy.
| Field | Description |
|---|---|
| Template (required) | The event template that defines the event's structure, including its name, attributes, and display settings. Select an existing template from the dropdown or click + New Event Template to create one inline. |
| Allow Ack | When checked (default), operators can acknowledge events generated by this analysis. |
| Severity Level (required) | The severity of the generated event. Options typically include Warning, Critical, and others defined in the system. Defaults to Warning. |
| Reason Code | An optional enumeration value that classifies the reason for the event. Reason code options are defined in Libraries → Enumeration Sets. |
| Reason Code Value | An optional sub-value within the selected Reason Code. Available after a Reason Code is selected. |
| Event Filter | An optional condition expression that determines whether the current trigger should create an event. An event is generated only when the filter condition is satisfied. Useful for suppressing routine results and emitting events only for abnormal conditions, limit violations, or state transitions. |
| Min Send Interval | The minimum interval for sending notifications after events are generated by the same analysis. Defaults to 15 minutes. It limits notification frequency to prevent notification flooding when a condition persists. This setting does not determine whether the event itself is created. |
7.5.3 Capturing Calculated Values in Events
When event generation is enabled, the Event Attribute column becomes available in the Output Attributes table (section 3). This feature allows capturing the computed value from the analysis expression directly into an event attribute at the moment the event is created.
For example, if an analysis computes the maximum voltage during a window, the value can be written to both an element attribute (for time-series history) and an event attribute (recorded with the event). Each output row can be independently configured to write to an element attribute, an event attribute, or both.
7.5.4 Relationship to Event Templates
The event template selected here determines the following:
- The event name and display label
- Which event attributes are available in the Event Attribute column
- How events generated by this analysis appear in the Events tab
Events generated by analyses appear in the element's Events tab alongside manually created events, labeled with the analysis name as the source.
If an Event Filter is configured, the system evaluates it before creating the event. An event is created only when event generation is enabled and the event filter condition is satisfied. The Min Send Interval applies only to notification delivery after the event has been generated; it is not a prerequisite for event creation. Therefore, even within the minimum send interval, qualifying triggers can still create events, while notification delivery remains subject to the interval. This behavior does not affect the analysis calculation or output writes.
