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, select the product of your interest in the left column. Then 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 will first be moderated before they are made visible to other users of this portal.
This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.
Thanks Sean. This fits with what we are seeing is that there are some elements of the description that can be moved to things like device and station, and then the relationship of the point to those higher level objects can be shown to the operator in context.
In other words, normalise this information using the available objects and relationships that the product supports, which will eventually be part of a Unified Name Space asset model.
The customer is attempting to store details of the specific point to enable the operators to more quickly identify the point and its purpose. Please see the attached example.
We have had this request a few times, and we have asked the customer what they are trying to store in the description fields. What we have seen so far is information like station and pipeline which are better stored in other ways, like creating a station in the station table, or by using POLIQ features and linking the point to that instead.
Could you please elaborate on what the customer is trying to store here?
Also, you can invite the customer to engage on this portal directly.