Skip to Main Content
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.

Status No status
Product PI Connectors
Categories PI System Connector
Created by zachary cmelak
Created on Feb 25, 2025

PI System Connector should be able to Parameterize AF objects (like attributes) to dynamically update between environments

In Asset Framework, we are able to use substitution parameters to define PI Point Data References because the variable is able to resolve based on the template.

PI System Connector is used to synchronize, and keep perfect copies of the assets between two Databases. But if things cannot be configured from the Data Collection Manager, then it can't be adjusted.


This leads to different templates being required for PI Point if used between a DEV and PROD system, as there is no way for the templates to dynamically update between two different environments.


PI System Connector should be able to select certain parameters in it's environments that can dynamically update based on where a change was made.

i.e.
PARAM1 & PARAM2
%PROD% & %DEV%

in AF Element Templates, this would allow the PI System connector admins to change element attributes on the fly between environments. Users would be able to make changes in DEV to push to PROD, and inevitably clean up PROD to keep perfect copies of it in DEV.

This could extend for further uses, and allow some additional configurability to update based on the environments edits were made in, while maintaining the necessary requirements that allow for basic functionality and minimize the number of DEV only / PROD only

Similar products incorporate this use case, like Octopus Deploy.


  • Attach files
      Drop here to upload