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.
As others have mentioned the ability to connect PI to certain MES' as well as other 3rd party analytic tools and also ERP's.
We would use the OPC UA server to securely send values to the DCS. The DCS system only supports the UA protocol and not the DA. An example is to read the APX prices to control energy production.
PI OPC UA server will make the integration with our MES systems more easier than using PI OPC DA Server, hope can implement soon.
The PI OPC DA server adds the DCOM pitfall to which no organization would want to fall and this makes it more difficult to use this feature having to always install it on the "client application PC\Server". PI OPC UA will enable a REMOTE connection and a viable and secured one.
PI OPC UA server will make the integration between MES (+other systems) & PI easier for real-time handshake which is almost always necessary between such systems. Often MES needs to write a feedback value to Historian, a trigger for a calculation or a Boolean resetting a flag, etc. Relying only on proprietary connectors provided and not enabling the likes of OPC UA (and MQTT) just makes the integration harder on organizations and that reduces the probability that an organization will continue to have an incentive to rely on the platform not being able to integrate it easily with other platforms.
Please reconsider your stance on this feature. OPC UA Data access would bring PI up to the latest technology and security.
It passed 2 years when this feature was declined and OPC UA became to completely smashing OPC DA from the market. Any wrappers between DA to UA are not sufficient Today and become to be a disappointment for clients using PI. Have You reconsidered this feature already?
Fully supporting the need for PI OPC UA Server. A lot of customer want to switch to OPC UA for other client that reads data from PI Server. Now they need to implement a third party solutions using Cogent Data Hub to wrap PI Server as OPC UA server or APIS that connected to PI OPC DA Server and wraps it as OPC UA.
With PI OPC UA Server instead of PI Data Archive only as it was for PI OPC DA/HDA Server the PI OPC UA Server can expose AF structure as well as OPC UA address space, that would be really helpful.
Shame it was declined.
This enhancement definitely should be revised and reopened now. OPC DA is almost gone from the market...
It's a must for as, in addition, it is also a must for the product longevity if you want to have the same features other historians provides nowadays.
Definitely a must have in industrial environments going forward. OPC UA is the technology to integrate IT with OT bidirectionally. Businesses and integrators are increasingly requesting to have PI data in their applications with preference to pull data from PI using OPC UA.
Without OPC UA Server as a product in the AVEVA PI Suite, other third party products needs to be considered to enable IT/OT integration, what is adding more complexity, costs an unnecessary IT footprint.
But maybe more importantly for AVEVA, it paves the way for other integration products in the landscape and the first step to stop using PI.
Agree that this is definitely a must have. Everything OPC is moving towards OPC UA as its better security and easier to use. Really surprised to see that this request was Declined as seems like a no brainer to add to the offerings for PI.