Skip to Main Content
AVEVA™ PI System™ 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, 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.

Status No Status
Categories Security
Created by Guest
Created on Aug 20, 2022

Change process to release security patches

Hello, whenever Osisoft identifies security issues on PI / PI AF, they deliver fixes through the next release of these applications. This is not convenient as upgrading to a new release is a risk that we don't like to be forced to take and has a cost (we manage about 40 PI servers WW under different versions). We would rather appreciate to have patches applicable to our versions of PI. This is what software vendors usually do. Could you please consider managing your future security patches this way?
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    I'm not yet seeing how this helps in keeping the cost down. In all cases you have to test before deployment to stay in control, if it is a version upgrade or just a security patch.   I do agree that new versions include new functionality and could break existing functionality (seldom, but it does happen). So there is some merit in that