Kontakt z INEE - Polska:
Telefon: +48 32 235 45 60
Odwiedź nas: www.inee.pl
Zapytaj o...
Pobieranie zasobu
  • KWS-ALMEV0-SUB - Subskrypcja dla Alarms & Events
    KWS-ALMEV0-SUB - Subskrypcja dla Alarms & Events
  • KWS-ALMEV0-SUB - Subskrypcja dla Alarms & Events
    KWS-ALMEV0-SUB - Subskrypcja dla Alarms & Events
Subskrypcja dla Alarms & Events
316.00 $
12 mc
KWS-ALMEV0-SUB - Subskrypcja dla Alarms & Events
Alarms and Events for KEPServerEX can help reduce costs and improve performance. OPC Alarms and Events (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.
Informacje dodatkowe
Item Browsing and Importing
Browse KEPServerEX 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.
Full OPC AE Client Severity Support
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.
Extensive Alarms and Events Condition Support
KEPServerEX 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.
The multilevel condition supports multiple sub-conditions. This condition is used if the source has multiple states of interest and there is a need to know the transition between the condition states. For example, if you have a temperature tag with multiple temperatures of interest, use this condition. The HIGH_HIGH sub-condition has the highest priority and the LOW_LOW sub-condition has the lowest.
These are single level conditions with a sub-condition that matches the condition name. These conditions are used if a single state of a source is of interest. For example, if you have a temperature tag with a single temperature of interest, use this condition.
Note: Use HIGH_HIGH for higher priority states and LOW_LOW for lower priority states.
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.
Port komunikacyjny
OPC plugin
Produkty powiązane
KWP-ALMEV0-PRD - Alarms & Events
KWP-ALMEV0-PRDAlarms & Events