Support Alarms and Conditions
Support for Alarms & Conditions. This data type would be good candiate for storing into Event Frames. Tell us more about your use case in the comments, which source system you have that support A&C, and how you would select which A&C to collect/not collect. How would you like Event Frames built and named?
We are currently evaluating how to appropriately and effectively bring this functionality forward. We are working through details pertaining to implementation of this functionality.
Dirk De Vocht commented
Alarms and Events data from automation systems become more and more important to store for long term. This demand comes from the need to optimize processes through data analytics and data modeling tools. Ideally this Alarm & Condition data is store in the same data repository as trend data.
Moving from OPC Classic to OPC UA is key as we have systems that are not providing the OPC Classic interface. When the PI connector is not supporting the Alarm capturing, we'll need to setup other systems that does provide the OPC UA Alarms & Conditions and long time storage capabilities.
Seconding Yusuf Cördük's comment, it would be great to have the option to choose between EF storage and PI tag storage for the Alarms and Conditions.
Our end users prefer to have the Alarms data as strings in PI tags.
Johan Van Acker commented
For the moment we work with the OPC A&E interrface to get alarms out of Siemens WinCC, but that is not very fexible. So the OPC UA connector should have at least the same functionality, preferable more like eventframes for alarms, one PI tag for all the messages, ...
We would appreciate if there would be a possibility to choose between Event Frame storage and PI Tag storage, or even both at the same time.
Björn Molin commented
Any news or update regarding this, this is a must when going OPC-UA.
Could you share any viable workarounds this would be apprichiated.
What is the status regarding this function?
We want to collect Alarms and Conditions from Siemens 840Dsl_828D_OPCUA
This is critical for discrete manufacturing
Andreas Wenzelmann commented
we are using WinCC and other System as SCADA. Today we import the Alarm Data to an Pi Tag with the format String. The different colums from the scada system we sepaerate with a pipe symbol. For history this is fine. But in case of reporting and analytics this is very bad.
I would be happy if there is an oportunity or a speicial pi point format for alarms.
The nessary coloums are:
- Alarm ID
- Status (Start, End)
Currently we are using OPC AE and storing the events in Event Frames. When we move to use OPC UA we need to start to work with Alarms & Conditions instead!
Also i want a way to native create Event Frames within the Connector for OPC UA.
Tjeerd Zwijnenberg commented
Important for Rail industry, so yes
we also use WinCC and other scada systems. about what to collect/ not collect, there should be same filtering possible like in the scada system itself, so i want the possibility to filter on every attribute the scada system offers. Naming for event frame should also be possible. E.g. Asset_Alarmtext or Alarmtext_Messageclass,...
The eventframes should be built without using PI Tags (Tagrefference). The behaviour of the end of eventframe (end eventframe when alarm is gone or with quitting) should be configurable in the connector
Hi! We are about to do a pilot with alarms and events to let them be stored into event frames!
I heared it was a new product from OSI regarding this issue! We want to be involved in a Beta test.
We use Siemens WinCC and ABB 800 xA DCS systems.
//Magnus Holmbom, Vattenfall Vattenkraft AB