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.
My large customer, with many sites and limited support personnel, struggles to turn over the ongoing care of Adapters once they have been correctly installed by the support staff who cannot return to maintain them as the data source (and tags to collect) change over time. Providing a GUI for these maintainance-type tasks, would allow the local staff to maintain their own data sources.
I think the GUI should be an optional extra selected by the user at install-time, or a seperate install package altogether.
Part of the appeal of the adapters is the light weight. Adding a GUI would add bloat and consume resources on the hosting machine. Further considering that AVEVA's recent GUIs have been web portals which recommended Google Chrome, this would also be another source of bloat.
Another possible downside to having a GUI is that its more code to be maintained (look at ICU), and with the intention that the adapters are cross-platform a GUI may introduce additional complexity. Not a dev, so would be happy to be corrected.
One thing AVEVA could do to help users is to publish a Powershell script which will take a folder of JSONs and push them into the config as needed. For Linux the equivalent shell script can be provided. These would be open source and provided without guarantee, so maintenance of the code would not be a key factor in the adapter core functionality. I was also freaked out the first time I started an adapter, but after cooking a little powershell I much prefer it than e.g. the connector / DCM / relay webUI.
Another improvement requested elsewhere is to allow the config to be done from a remote machine and authenticated with Kerberos.
Hi Jiyeon,
For those of us who do not want to expose our systems to the internet, it would be better to have a GUI that is available on the machine that the adapter is installed on to allow for adding in Tags/Streams and be able to modify the configuration there without requiring a tenant and network connectivity. Otherwise, there are a whole host of customers who cannot consider the PI Adapters if they have to be open to the internet.
Thank you for your feedback. This is something we have heard from other customers as they evaluate which data connectivity product will suit their needs. While I do not have a timeline for when we will be looking at migration paths between PI Interfaces or PI Connectors to AVEVA Adapters, it is on our radar and we will do our best to make it a positive experience for you.
Related to this topic, we do have an offering via AVEVA Data Hub called Edge Management, which allows you to remotely deploy Adapters and Edge Data Store using edge modules. There is also a software management component we are working on to make it easier for you to manage Adapters and Edge Data Store instances from one central location in AVEVA Data Hub (regardless of whether you deployed them using Edge Management or not). These offerings do not require you to use AVEVA Data Hub as the data endpoint, but you will need a Data Hub tenant and network connectivity to the Adapter/Edge Data Store device.
If you have specific needs from the user interface, please share them in the comments so that we can have better insight into your expectations.