7.5 Generating Events
The Event section (section 3 of the analysis form) controls whether the analysis creates an event each time it fires, along with the event's structure, severity, and delivery policy.
7.5.1 Enabling Event Generation
Whether an event is generated is determined entirely by the Event Template field:
- Select an event template — event generation is enabled, the other event fields become available, and an Event Attribute column appears in the Output Attributes table of the Calculation section.
- Leave Event Template empty (None) — no event is generated.
7.5.2 Event Fields
Once an event template is selected, the following fields are available to further define the event's severity, filtering, and delivery policy.
| Field | Description |
|---|---|
| Event Template (required, when generating events) | 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. Leave empty to skip event generation. |
| Allow Ack | When checked (default), operators can acknowledge events generated by this analysis. When the Event Window trigger is used with multiple Start Trigger rows, the Allow Ack of each child event is set per Start Trigger row, and this field has no effect. |
| Severity Level (required, when generating events) | The severity of the generated event. Options typically include Warning, Critical, and others defined in the system. Defaults to Warning. When the Event Window trigger is used with multiple Start Trigger rows, the severity of each child event is set per Start Trigger row, and this field has no effect. |
| 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
Once an event template is configured, the Event Attribute column becomes available in the Output Attributes table of the Calculation section. 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. The system creates an event only when event generation is enabled (the event template is not empty) 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.
