PI Server

Welcome to the PI Server feedback page!

We created this forum to hear your ideas, feature suggestions and feedback on PI Server. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.

Please note that your ideas and comments posted here are visible to all other users.

  • For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal  (https://my.osisoft.com) instead of sharing them on this site.
  • For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Make a way to know the statistic of use of every PI TAG in Data Archive

    When you have thousands of tags in your Data Archive, you need to know wich tags are beign used and witch don't. It would be very usefull to have some diagnostic that shows wich tags are being cosumed more and from wich client.

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  2. PI Data Archive - import tags and merge historic archives together

    As a customer who is moving their PI Data Archive historic data to a Centralized IT Facility, hosting another PI Data Archive, and that would like to import tags and historic data from another PI Data Archive, it would be great to have a functionality on PI Archive Subsystem and PI System Management Tools that allow to import PI Points and their historic data to the centralized PI Data Archive without having to perform all the steps for the Merge procedure.

    Another option would be to have an improved PI Base, Snapshot and Archive Subsystem services, that allow to have…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  3. Auto Archive Management - Shift vs. Delete

    Currently, there are two methods to 'shift' archives:
    1. "ArchiveAutoArchiveFileRoot" set to blank
    2. "Archive
    OverwriteDataOnAutoShiftFailure" enabled
    Neither method shifts to dynamic archives. We have three sites that merged PI servers, thus half our archives are merged and dynamic. this negates any automated form of archive management.
    I suspect the two shift methods came about thru an evolution, but there should be a way to 'rotate' thru all archive types so that we don't need to manually manage archives, mess with additional drives, etc.
    What about a new tuning parameter?: 'Archive_DeleteOldestOnAutoShift'
    We are only required to keep 'x' number…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  4. Include usernames in pidiag -xa export of PI Archive audit trail

    As a PI Administrator in a regulated environment, it would be helpful if the Archive audit trail data exported by the pidiag -xa command included the username associated with each action. Currently, the pidiag -xa exports of archive audit logs do not include the associated username for archive edit operations.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  5. AI Detection for Stale Points

    As a PI System administrator, it would be helpful if the PI Server had an artificial intelligence or machine learning system which could recognize the normal updating patterns of a PI Point and report when a tag was not receiving updates properly to the administrator. The present method for identifying stale points requires some knowledge about how frequently each point would be expected to update.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  6. Restore Write access to Module Dabase after uninstalling AF link

    MDB to AF synchronisation is not needed anymore and new installation of data archive are free to not install it. Existing installations must maintain this link in order to allow PI-ACE to function properly and add new context. PI-ACE cannot be replaced by AF Analysis in certain circumstances. It should be possible to uninstall AF-link and restore write acces to MDB as of if it were never installed.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow specifying a range of older archive files to backup in piartool

    The piartool -backup command has multiple parameters that allow for specifying a number of archives to copy. For example it is possible to specify a number of archives to backup starting at the current time (-numarch), or each archive number can be specified in a list (-archives). But no parameter will allow specifying a numeric range of older archives to copy, such as from archive #500-1000. It is also not feasible to list out each archive for the -archives command when there is a large number of archives desired to copy (500 501 502 etc.)

    If it was possible to…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  8. PI Tag Name Search Count recorded in PI Tag

    Could the feature of counting the number of pi tags (by prefix) and display it in PI Tag or PI Vision. In Microsoft Excel's PI Builder, I would query for pi tags starting with "dist*" and get a count.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  9. Built-in feature to automatically move archive files past a certain age to a different directory

    Automatically move archives from a disk to another based on their age. Use case: I only want to keep the last 2y of data on a SSD and the remaining will be stored on a regular disk.

    My use case can be achieve using the example PowerShell script located at "%pihome%\OSIsoft.PowerShell\Example Scripts\MoveOldArchives.ps1" on any machine with SMT installed. I would like to see this feature built natively into PI System Management Tools.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  10. Refresh button for the Interface Configuration Utility (ICU)

    When doing certain changes within the ICU (like configuring buffering for an interface) the end user has to close out of the ICU and then open it back up just for the ICU to refresh and reference change within higher versions of the ICU that have the buffer manager included. A refresh button included with the ICU could prevent the unnecessary step of having to close out of the utility and then opening it back up just to see the change.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  11. Enable Data Fanning for PI Collectives through PI System Management Tools

    Currently, PI System Management Tools supports buffering but not data fanning (does not send data to all collective members).

    When using a PI Collective, customers would like to make changes to PI Point values in Archive Editor in the Primary Data Archive and see those changes replicated to the Secondary Data Archive when buffering is enabled.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  12. PI AF Link & PIBatch - Ability to uninstall it

    PI AF Link is not included in PI 2018 but it would be good to be able to remove the link during an upgrade. (not possible today https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=000027668).
    Same for PIBatch which cannot be uninstalled even when not licensed for (recommended to disable service https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=PIBatchsubsystemdoesntstartBatch)

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  13. Change Flat Data to No Data if PI Interface to PI Server Connection is lost

    Problem:
    iIf PI Interface disconnected from PI Server, PI Point will show flat data until connection up not No data or Disconnected

    Propose Solution:
    Pl Server have ability to change flat data to no data if PI interface disconnected from PI Server. It will make misunderstanding if PI Point show flat data. In example level point from ATG Sensor, flat data could be that level on standby, but reality connection to PI server is lost

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  14. Have an option to use step interpolation to the previous event

    When the Step attribute of a PI Point is "on", PI assumes that a value is constant until the next event, which works well in most cases.

    For PI Points that track rolling averages, rolling totals, real-time derivatives of totalizer tags with respect to time, etc., it would be more useful to assume that a value is constant up to the previous event. Please add this as an interpolation option for PI Points.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  15. Improve PI Server Installation kit: disk space requirements should include the minimal PI Backup

    When calculating the disk space requirements on a recent upgrade the drive was expected to have only 138 MB installed. But the install failed due to not enough disk space on the drive because the minimal backup needed a certain amount of disk space. This need should be included in the Required Disk Space panel when upgrading.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  16. Separate priority setting for Data Read and Data Write

    Data Read and Date Write (Buffering) from/to PI Data Archive is based on the priority settings in PI SDK and PSE. We have a architecture of 6 member PI collective and all the source data is not buffered to the individual collective. Hence for other applications like PI Analysis or any other 3rd party applications data read should from couple of collective members and data write should be to 4 collective members.
    As per the current setup, if we enable the priority for 2 members in collective, data read and write is happening only for those members (Default behavior). But…

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  17. Optimize the storage and retrieval of digital tags

    Given that the archive file format is proprietary, this suggestion is me shooting in the dark.

    Disk compression compresses archive files very well, and my guess is that most of this compression occurs on the digital tags, since the number of possible values that they can take on is limited. In contrast, the number of possible values that a floating-point tag can have is huge, so there is not much opportunity for compression.

    Please consider optimizing the storage of digital tags so that their data takes up less space in the archive and can potentially be retrieved faster.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  18. Optimize and compress non-primary historic archive files

    Currently, the same file format is used for primary and non-primary historic archive files. This does not make much sense since the two types are used very differently.

    For the primary archive:
    • Write operations should be fast since it is collecting data in real-time
    • Read operations should be fast since the most recent data is usually the most relevant
    • File size is not a concern since there is only 1 primary archive

    For non-primary archives:
    • Write speed is not a concern since write operations are infrequent
    • Read operations should be fast because users may want…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  19. Compress archives that are backed up using "Copy"

    Currently, when a "copy" backup occurs, the archives are copied as-is. Archive files take up a lot of space, but they also compress very well, and since archive backups are rarely accessed, it makes sense to trade off increased access time (due to the additional work of decompression) to get a smaller file size for the archive backups.

    The exact method of compression (new file format, put archives in a compressed folder, etc.) will be up to OSIsoft. In my testing, I used disk compression on the archive files.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  20. Replace the batch (.bat) scripts in the %PISERVER% folder with PowerShell (.ps1) scripts

    This replacement is appropriate for several reasons:
    • PowerShell is easier to read and is a more powerful language than the batch language.
    • Batch scripts are best used in Windows, whereas PowerShell is cross-platform. This replacement will support OSIsoft's expansion outside of Windows.
    • Microsoft is pushing for PowerShell and leaving batch files in the dust. Ideally, PI systems would not rely on legacy technology.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED