We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.
To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.
This page is for feedback specifically for AVEVA Data Hub. For links to our other feedback portals, please see RESOURCES below.
An upgrade from a Read-Only to a Read-Write solution would also be useful.
At the moment alarms and conditions are dependent how a user/administrator configures it in the PI System, most of the time based on tags and analytics. The adapter should allow to connect to OPC UA A&C and create Eventframes. The User/Administrator should be able to choose A&C attributes as EF attributes, as well as the primary referenced Element. If feasible, it should also be possible to configure the A&C as an subeventframe (e.g. subeventframe of a batch-eventframe).
Speaking from process industry point of view (food, chemicals, pharma)
-Alarms and Conditions are important to identify discrete events in time, imo this is just as important as the continuous data streams from metrology sensors. OPC UA adapters should be carrying all the features that the OPC UA A&C server is featuring.
-A&C can represent: Process alarms, warnings, events. But also operator actions and audit trails. I often miss the capability to represent this kind of data in a out of the box / native way(without bespoke development) in PI Vision for example.
-Right now we often need to connect to Relational databases to read A&E data, but that is not that evident since a lot of vendors don't give visibility into their data model, or have concerns regarding security and performance degradation of a RDBMS connection.
-Another backside is that we end up (from this relational database from the source) with a lot of string text in the PI data archive, but there is no relation anymore between the events. eg there is no inherent relation anymore between an event representing an alarm that has come up and gone away/acknowledged, except for the text or some alarm ID in the string.
-Also representation of A&E data is often via a custom solution. It would be great to have some configurable A&E element in PI Vision to represent alarms. I think way back there was something like the PI Alarm Viewer.
PS
--> obviously PI Event Frames can be used to configure and represent A&C, but:
-we often just want a reflection of the A&E data from the source systems.
-often this is just not realistic to create EF triggers for each possible source alarm
In Pharma industry, my company utilizes Alarms and Conditions (for OPC UA) and Alarms and Events (for OPC DA) for audit trail logs for different equipment. We currently utilize multiple 3rd party vendors to collect these data. I am quite interested to utilize PI adapters, connectors or interfaces to move these data into PI, so that we have single data historian for all our data. I am quite interested to see what the PI Engineers/Developers come up with.