Events¶
Events are created when specific predefined conditions for tag values or quality are met. They provide a way to monitor and track the status of various conditions. Events remain active until the condition that triggered the event is no longer active and, if configured as a requirement, the user has acknowledged it. Once an event is no longer active, it becomes a historical event.
If required, the system can be set up to send a notification to predefined users (internal or external) in case an event is triggered.
Event Scheduling¶
Events are processed according to the scheduled period and recheck period defined during event configuration (see Configure Events). This ensures that events are evaluated and managed consistently over time.
Condition Monitoring¶
Events monitor one or more conditions and can involve the same tag or different tags. Each conditional is evaluated to determine if the event should be triggered.
In case of multiple conditions, conditions are configured with an Order to control their precedence, with each conditional separated by AND/OR clauses. These clauses are simple in nature, with no parentheses or grouping capability. The conditionals must evaluate to True for the event to be activated and recorded in history.
Event Processing¶
The following image shows the main steps of event processing:
