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 Declined
Categories System Management
Created by Kenneth Barber
Created on Aug 19, 2022

Revise tuning parameter descriptions

As a general suggestion, please look through all the tuning parameter descriptions and fix any mistakes or inconsistencies between descriptions. This includes the ones that the user cannot see by default. All: Almost every tuning parameter description contains a string of the format "Value units are in [unit].". I wouldn't say that my mass unit is in kg; I would say that my mass unit is kg or that my mass is in kg. Consider changing this string to "Value unit: [unit]". Tuning parameters of the enumeration or bitmask type use inconsistent formatting with each other for presenting and delimiting each number/bit and its meaning. Consider using a new line as the delimiter. Replace "boolean" with "Boolean". Consider treating Boolean types as enumeration types (i.e. 0 = , 1 = ). Make sure that units are shown consistently (e.g. not "sec" in some places and "seconds" in other places). If the description is a single sentence fragment, be consistent in whether a period terminates it or not. Replace "periodically (once a minute)" with "once a minute". Replace "PI-SDK" with "PI SDK" and "PI-API" with "PI API". When 0 is a special case, consider treating the "0" and ">0" cases like enumeration values. General: EnableAudit - consider splitting into multiple lines for readability MMQ_LowDiskSpaceMB - replace ")(" with ") (" and specify who "support" is Archive: Archive_AutoArchiveFileSize - replace "a automatic" with "an automatic", replace ", You" with ". You", replace the 2 spaces with 1 space, consider rewriting entirely due to strange wording Archive_DataCoercionPolicy - consider splitting into multiple lines for readability Archive_DisableArchivingOnIOError - wording suggests that the tuning parameter enables a disable or disables a disable Archive_DisableArchivingOnIOErrorRange - replace all cases of 2 spaces with 1 space Archive_FutureAutoArchiveFileRoot - missing a period after "same prefix" Archive_LogArchivePercentFull - delete " (in percentage)" Archive_LowDiskSpaceMB - move "if this limit is reached" to the start of the sentence to make it clear that it applies to both of the clauses joined by "and" and not just the first one, replace ".." with "." Archive_MaxPrivateBytesPercentOfTotal - delete "Sets the " Archive_MaxQueryExecutionSec - delete "Sets the ", replace "0 has" with "0 indicates" Archive_MaxWriteCachePercentArcCache - delete "Sets the " Archive_ShiftRatio - replace "inverse" with "reciprocal" MarkArchiveGaps - consider splitting into multiple lines for readability Backup: Backup_LowDiskSpaceMB - replace the 2 spaces with 1 space, specify who "support" is, is the unit Mb (megabits) or MB (megabytes)? Backup_MaxHistory - delete " for which to save history" (you don't save history for a backup; you save history in or as a backup) Backup_TraceLevel - replace the 2 spaces with 1 space, separate the command into its own line for readability, misplaced modifier starting at "while" (it reads as if the overriding can be done when the command is used to run the Subsystem) Backup_UseSystemProvider - delete "there are " BackupVerification_NumArch - replace "by setting … 0" with "(BackupVerification = 0)" (otherwise it reads as if the parameter is ignored if verification was disabled by setting BackupVerification = 0, but maybe it would not be ignored if the disabling was set some other way) Base: EnableHostnameForFQDN - replace 2 spaces with 1 space PointDb_RemoveEmptySource - replace "startup" with "startup,", replace ". So" with " so that" Replication_ClockDiffLimit - "secondary" describes which noun?, what is "syncfailure"? Net Manager: Keepalive - should be renamed to "KeepAlive" for consistency with other tuning parameters, replace 2 spaces with 1 space MaxAuthAttempts - delete "Configures the " Snapshot: Snapshot_AnnotationSizeLimit - is it in kilobits or kilobytes? Security: AutoTrustConfig - consider splitting into multiple lines for readability Server_AuthenticationPolicy - consider splitting into multiple lines for readability
  • ADMIN RESPONSE
    Aug 19, 2022
    Thank you very much for sharing your feedback on the PI Server. After further evaluation, we have decided to decline this item, as we are not planning on implementing it in the near future due to other high priority items across the PI System. Thank you for your feedback, and know that we are listening and reviewing every item that gets submitted!
  • Attach files