⮫ “Object: Alarm Configuration ”

This is the required base object of alarm management. When you insert the object below an application, it is automatically named “Alarm Configuration”. Below that, objects for the “Error”, “Warning”, and “Info” alarm classes are also inserted automatically, as well as for alarm storage (“AlarmStorage”). You can adapt this structure. You can remove objects and insert other alarm objects.

⮫ “Object: Alarm Class ”

In this object, general alarm criteria are grouped into a class. Then the configured classes are available for selection in the editor of the alarm groups in the “Class” column as a "basic configuration" of an alarm. You can insert any number of alarm classes in the alarm configuration. The “Error”, “Warning”, and “Info” classes are automatically inserted first with the “Alarm Configuration” object.

Examples of alarm criteria:

⮫ “Object: Alarm Group ”

In this object, alarms are created specifically (alarm definition) and grouped together. Therefore, each alarm is unique. The alarms of a group can have a shared deactivation variable and shared archiving parameters. You can insert any number of alarm groups in the alarm configuration. You can use folder objects to organize alarm groups hierarchically. A text list with the same name is created with each alarm group. There you can localize the alarm messages.

⮫ “Object: Alarm Storage ”

The object is possible only one time per application. The archiving of alarms is configured in this object.

⮫ “Object: Remote Alarms ”

The object is possible only one time per application. The remote alarm configurations with the remote alarm groups and classes are managed in this object. The information is prepared by the data sources. In the case of this "distributed alarm management", the monitoring, alarm triggering, and execution of follow-up actions on remote PLCs are performed here.