AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


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 PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status No status
Product PI Connectors
Categories PI Connector for OPC UA
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Switch for using Name of AF Attributes from Browsable Name or Display Name

Add a Switch to the OPC UA Connector that we can choose if we want the AF Attributes to be created using "Browsable Name" or "Display Name". Using the Display Name would make it much easier for us to locate the Attribute and refer to its OPC Tag as we can see the same "Display Name" in both PI System Explorer and OPC Tools.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    Actual issue is: The OPC UA IF is NOT browsing the Information Model. It is browsing the address space to reinvent the classes of the objects to create the AF structure. Siemens SPPS T3000 has a huge structure on OPC UA Server and they use different names for attributes and variables, so the type identifier differs from the name of the Information models class. This result in a strange behaviour: For example: Information model describe a Motor modul. In Address space we have 100 Motor modules, each object has a different name. In AF, ONE template is created with 100 attributes. In Elements, each Motor has 100 attributes where only one Attribute is active and the rest is excluded. Furthermore, without Special handling, the OPC UA IF is producing a 15MB csv file which could not be handled by the Interface itself and it is nearly impossible to maintain that csv file! My Suggestion is: A Switch in the config file to browse the Information Modell to create the type Definition file. The user can then select the classes he want to get. If Interface is starting subscribing it filter out only these objects that was derived from the type definitions in the Information model. Each object carries Information about the type Definition behind and each variable carry original name from Information model in "Browse-name" One tricky Point is then still open: Should the Interface create AF templates based in the Information model? I believe yes as it perfectly relates to the object orientated model of OPC UA, but If real objects are created as elements, they have the Attribute names as described from the template. In real world, the attributes were renamed! In summary: Yes, i want to get this fixed asap, as Siemens distributes the new T3000 V8.1 and up, which ONLY supports OPC UA.
  • Guest
    Reply
    |     Aug 20, 2022
    And by the way: Connectors doesn't care about Pointsources, Instrument tags, Location 1-5 etc any more. To be honest i don't understand in which direction osisoft want to develope the connectors. the "old" solution gave us the possibilities to change the datasource by changing Location 1 or pointsource. Even more, we were able to name the PI tag different from sourcetag. I can't see how i can do that with the OPC UA connector...