Alarms and Events for Kepware can help reduce costs and improve performance. OPC Alarms and Events (OPC Classic AE) clients can receive and monitor process alarms, operator actions, informational messages, and tracking/auditing messages directly from Alarms and Events. Users can monitor areas of a process that may require operator attention when defined thresholds are met, including safety limits of equipment, event detection, and abnormal situations. Alarms and Events can also be used to help identify faulty equipment, create maintenance work orders, and improve operators' effectiveness. Furthermore, it can be used to collect and record alarm and event information for audits or used in correlation with other historical data.
Alarms and Events is an advanced plug-in to Kepware's industry-leading connectivity platform and works in conjunction with the included OPC AE server interface. Creating an alarm is as simple as browsing the existing tags and selecting the item that will be used as the alarm. Once an item is chosen, a condition and sub-condition need to be set for the item. A trigger is then set comparing the current data value and the threshold. When the condition's trigger is met, an alarm will be sent to the corresponding Alarms and Events client application providing the user with unique alarm input, output, and acknowledgement messages.
Browse to find and import available tags for testing. Tags can represent specific areas and equipment on the plant floor. To make third-party OPC DA and OPC UA Servers available for use with Alarm and Events, use and configure the OPC DA and/or OPC UA Client drivers.
The severity value is an indication of the urgency of the sub-condition. This is also commonly called ""priority,"" especially in relation to process alarms. Values range from 1 to 1000, with 1 being the lowest severity and 1000 being the highest. Typically, a severity of 1 would indicate an event that is informational in nature while a value of 1000 would indicate a disastrous event.
Supports nine OPC AE standard conditions, providing flexibility in how Alarms and Events Conditions are calculated and prioritized. Each condition has a unique name and a unique set of sub-conditions.
This condition compares the source data to a static or dynamic ROC. For example, if you have a source tag that represents production output and you want to trigger the condition if the output falls below 100 units a minute, use this condition.
Note: Use ROC_HIGH for high priority conditions and ROC_LOW for low.
Delivered as a standard feature, Kepware exposes Event Log data (events) to OPC AE client applications. The Event Server works in runtime and service modes, supporting three event categories: Information, Warning, and Error. The interface also includes Alarm and Event Conditions.
Import and export tag data into a Comma Separated Variable (CSV) file. Using CSV import and export creates tags quickly in the desired application.
Filter by area, source, event type (simple and conditional), severity, and category.
Enable and disable communication areas, sources, and conditions through the Alarms and Events user interface.
Create unique alarm input, output, and acknowledgement messages in addition to alarm acknowledgment rules.