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.

Add a new idea Subscribe
Status No status
Product AVEVA™ PI Server
Categories Asset Framework (AF)
Created by photi24
Created on Aug 19, 2022

RELATED IDEAS

Multi Language Support for AF Elements and Attributes

We use PI in an multilingual context. Therefore we need an functionality to support. It would be good if you could enter a translation list for several languages for all elements and attributes. This language must be selectable and accessible via all interfaces as well as via PI VIsion.
  • Attach files
  • Jeccie Qiu
    Jul 21, 2025

    This a great idea for the PI Batch Interfaces. Since PI Batch Interfaces don't fully support Unicode languages, we could generate the EFs using English version of AF database and consume EFs and Assets data in other language.

    Reply
  • Alistair
    May 28, 2025

    A basic version of this could be implemented if assets and attributes had access to the connected user. We could then implement 2 AF tables with table-lookup attributes:

    A global User Language attribute does Select [Preferred language] From UserPreferences where User = %CurrentUser%

    Then each attribute has child Localised Name and Localised Value (for string or digital state attributes) to look up the localised name or value from a second Localisation table using the global User Language attribute and the parent attribute name or value:
    Select [Localised String] from Localisation where [String] = %..|Attribute% and [Language] = %\Globals|User Language%

    So the only update we need for this is access to the connected user. It's clunky but I think it would work.

    Reply
  • photi24
    Sep 4, 2023

    We need several languages.

    English, French, German, Italian

    The best would be, if the langeage is configurable.

    Reply
  • DanielNeu
    Aug 28, 2023

    This topic would be very important for us to have global cockpits used from China, India, Europe, US and Brazil - so many languages.

    Reply
  • Admin
    Kevin Geneva
    Aug 25, 2023

    While we are working towards creating a new integrated delivery of our MUI kits for the next PI Server release, the next release of PI Server will not have the ability to show custom language support for user-defined fields. I apologize for the confusion and change in direction for this idea.

    Reply