Hyper Alarm Server Overview
Hyper Alarm Server™ converts real-time and historical data to alarm messages generated by alarm sources within your process/industrial control system. The server uses the latest .NET technologies for better performance, such as built-in redundancy, asynchronous processing, and the ability to access historical and third-party data. In addition, Hyper Alarm Server allows alarm customization, such as creating multi-limit alarms. Alarm types serve as templates for your alarm sources (alarm tags.) You define the alarm type and its functional behavior and structure and then link alarm sources to the alarm type.
Clients access Hyper Alarm Server through the FrameWorX™ server point manager which is directly embedded in Hyper Alarm Server. OPC DA, OPC AE, OPC UA or other standardized communication protocols are implemented on top of the FrameWorX server and include individual point managers.
Hyper Alarm Server Integration with AssetWorX
It's recommended that you first configure all equipment assets or use the BulK Asset Configurator tool to accomplish the task.
When Hyper Alarm Server configuration gets installed into the same database as AssetWorX, the Hyper Alarm Serverdatabase mirrors the address space of AlarmWorX. This allows alarms to use the AssetWorX equipment properties to link assets to the Hyper Alarm Server.
Alarm sources (tags) that are linked to multiple equipment areas are considered a single alarm by Hyper Alarm Server and are counted as one alarm and viewed as one alarm type and one alarm instance. Additionally, you no longer need to use an alarm template (a set of alarm rules and conditions) to create multi-level alarms. For more information, see Hyper Alarm Server vs. AlarmWorX64 Server feature comparison.
Hyper Alarm Server's real-time alarm data is used by Hyper Alarm Logger which collects and subscribes to configured alarm sources through data connections, such as OPC UA, Modbus, or BACnet with, and logs the alarms and events to storage files.
What's Next: