Concepts, terms and definitions

Terms and abbreviations

IAA	Intelligent Alarm Application, The combination of the Alarm Dashboard and the Rule Editor is referred to as IAA.
Rule Editor	The Rule Editor is a graphics programming tool based on the IBM Node-RED Tool. It connects nodes to a program (flow). For Climatix IC, intelligent preset Siemens function blocks are supplied with the Alarm Dashboard for intelligent alarm handling.
	Dashboard for active Alarms↑: Overview of all active alarms at Tenant level without having to search through hierarchical plant lists. Focus and prioritize! Filter by date (by default the current week). Sort and filter by attributes, e.g. by alarm priority. Filter by alarm type to hide unimportant alarms and concentrate on important ones. Select an entry and go to the overview on the plant level. Note: Identical alarms are caused by repeated occurrence and disappearance of the error state.
	Dashboard for plant history: Overview on the plant level of all open and resolved alarms, grouped by type. Organize measures and research! Each entry displays a plant with an active or resolved alarm. Select the entry to go to the plant and view the active or resolved alarms and their context, the root causes and comments.
Tenant-wide overview of alarms	Faults and alarms are normally handled at plant level, but for a proper analysis, diagnosis and benchmarking, an alarm overview of the entire fleet of controller is essential. IAA provides this View.
Add to the knowledge base with comments	Whereas the routine for reacting to specific faults can be predefined by technicians, the input from users on site is essential to continuously improve the routines or to react to new developments.
Alarm fatigue	This is a widespread phenomenon. If numerous alarms occur, personnel become desensitized and no longer react appropriately. IAA offers powerful filters and prioritization tools to counter alarm fatigue.

Alarm Dashboard terms

Plants	IAA collects all alarms pending on a plant. All current and resolved historical alarms are listed and logged under the displayed plant. It is logged from the first occurrence of the alarm. Subsequent Plant Plant events↑ (e.g. acknowledgment of an alarm or the resolution of the root cause) are logged in the existing alarm and do not trigger a new alarm entry. INFO: Alarms must be closed in the plant. They cannot be closed via Climatix IC.
Root cause-related measures/recommendations	Predefined routines/actions that have proven useful for reacting to the root causes of certain errors. By defining causes, IAA offers a mechanism for outputting causes and recommendations as if-then rules.
Alarm type	An alarm type is an identifier generated from the alarm ID produced by SAPRO. The alarm type is unique to each application. IAA uses the alarm type as a trigger for diagnostic rules. *
* Background: The Climatix data architecture ensures that the same type alarm (i.e. with the same root cause) is reported using the same Alarm ID. An application made known in the IAA/Control Editor by 'Application Set Synchronization’ ensures that Alarm IDs coming from plants with this application have the same root cause.

Rule Editor terms

Node	Predefined functions blocks selected from one or more libraries.
Customized Siemens nodes	For pre-programmed nodes for the IAA application; this library is constantly being expanded.
Flow rate	Link of multiple nodes to become a program function. A simple flow forwards, for example, information from input 1 to output 1. A programming function can be extended to any level of complexity.

Climatix Alarm IDs

Alarm ID	The Alarm-ID is created within the controller↑ application and has no direct reference to a Cloud element, e.g. the application set. The relationship is established through the connection of a SAPRO application with the Cloud application set, but not directly. The Alarm ID is generated from the SAPRO object type, object ID and Member ID.
Alarm_ID properties	The Alarm ID is unique within a controller and an application version or application type. The Alarm ID per object may differ on controllers with different applications. The Alarm-ID can be identical in different applications if the same object type and Object ID are used.
Tips for engineering root causes	Note that the Alarm ID refers to the member and a member can have different states resulting in different root causes (e.g. analog value: "below range" or "no sensor"). Check whether identical Alarm IDs can exist in different application (sets) if set to = "ANY” in the Rule Editor.

Symbols

Active alarm	In plants: At least one alarm is active. In systems: At least one assigned plant is in alarm state.
Alarm already closed	A past alarm that is closed and recorded in the plant statistics.
Alarm closed	An old alarm event is recorded in the plant statistics.
High plant trip	Indicates a high-priority alarm.
Med partial trip	Indicates a medium priority alarm.
Low event	Indicates a low priority alarm.
Manually reset request	Indicates an alarm that need to be reset manually.