Introduction:
Adroit SCADA has some advanced alarming strategies, functionalities, and features. That said, sometimes the users use the alarm and AlarmList agent incorrectly, which in turn compromises the product performance, and in turn, affects SCADA application performance. This topic is merely intended to provide a holistic idea of what SCADA alarming entails.
Background of SCADA alarming (and events)
Some important principles to consider when it comes to the utilization of Adroit SCADA for notification purposes.
A distinction between alarms and events is to be drawn. Herewith some guidance.
Event State Notification Options
Alarms monitor agent tags, which usually represent event states. These need to interact with the user, as is the function of an HMI. In adroit, there are options:
Note where the alarm, AlarmList, and the applicable alarm routes fit in this architecture.
Alarming a Tag
The following is a simplified diagram depicting the utilization structure of how to utilize the alarm and alarm list agents in the correct order to alarm an agent.
Events vs Alarms – An example
To demonstrate between the two notification types, being alarms and events, the following diagram provides some clarity.
This is a practical example of monitoring tank levels – and when alarms and events as notifications is be used – as a principle, concept and recommended standard.