AVEVA™ Products Feedback Portal
Welcome to our new 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, 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.
It is worthwhile noting that a lot of us are looking at deployment functionality as the opportunity to transition from a plethora of solutions we've all implemented using external tools, scripting, cicode etc ... to something that is available out of the box within the product. It isn't there yet, and not being able to use it as an alternative to what has been done in the past will mean that the uptake of deployment will be limited (especially for the larger installations).
There is a clear need for the inclusion of improvements / enhancements to the deployment functionality.
- The solution should be able to automatically manage the update (ie deployment) to a client that has just become available after being unavailable for a period of time (eg workstation shutdown for extended period, comms loss, etc). Perhaps there could be a background task that checks the connectivity and deploy status of each client every x minutes (configurable), and then re-initiates the deploy to that client... minimising/removing the need for a user to be logged into the deployment app and doing all this manually.
- The solution should allow a 'roll- back' to a previous version without the extended delay that typically comes with a new deploy. Take advantage of the previous version being cached locally and already unzipped, just waiting there. It should be a 3 second restart, not a 3 minute delay whilst everything is deployed again. I understand there are potential security concerns in doing this, but there are other real-world concerns that seem to have been ignored. At least provide options that can be enabled/disabled.
- The solution could include a date/time (uptime, etc) status against each client on the 'Computer Tab', giving greater visibility of the status etc of each client.
And setting a time out time for the deployment server, has been asked before but still, it cost extra engineerings time to log in every time
And expand and collapse the versions of the grid. When you have multiple deployments it would be great to have this feature. And maybe a filter on the deployments for easier use when you have a lot of deployments and versions. It would help to avoid a lot of scrolling
And being able to remotely restart all servers from Plant scada studio would be great