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. Rearrange the Classic tab in the Point Builder to reflect the relationship between settings

    If the Compressing attribute of a PI Point is set to Off, then the compression settings are greyed out, which makes sense because they are irrelevant if Compressing is Off.

    However, if a PI Point has its Archiving attribute set to Off, nothing is greyed out, even though the exception and compression settings and the Compressing attribute are all irrelevant.

    I propose changing the layout of the Classic tab to reflect the relationship between these settings. If Archiving is Off, do not show the user the exception settings, compression settings, or the Compressing attribute. If Archiving is On, show the…

    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

    2 comments  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →

    When you select Archiving = off, no data is sent to the archives. However, the Compression settings still apply because these settings affect what is in the Snapshot. When a client application request the “current” value, the Snapshot is returned therefore it’s important to ensure the system knows and applies the Compression settings.

    Exception settings on the other hand affect how interfaces collect data, regardless of whether we archive the data or not on the server side. Exception settings are important to ensure that we are only collect data (on the interface side) that are significant. When an interface starts up, it connects to the Data Archive to get the points list and also the Exception configurations.

    With all that in mind, please provide additional details on your use case for this idea.

  2. Make the tuning parameter Base_AllowSIDLookupFailureForMapping visible by default

    When this tuning parameter is enabled, it prevents a PI Collective from being flagged as out-of-sync when some of the PI Collective members can resolve the SID of a PI Mapping and others cannot. However, by default, this tuning parameter is hidden and disabled.

    This tuning parameter is important when you are trying to replace all PI Trusts with PI Mappings to accounts that are dedicated to each instance of each PI service and you do not have the power to create domain accounts and/or the creation of dedicated domain accounts is not a priority for the organization as a…

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Make the tuning parameter PointDb_RemoveEmptySource visible by default

    This tuning parameter toggles the automatic deletion of unused point sources. By default, it is hidden and the automatic deletion is disabled.

    Point sources are used mainly for PI Interfaces, which are slowly being replaced with PI Connectors and PI Adapters, where point sources are less important. Therefore, it is also less important to keep this rather useful tuning parameter hidden. In the worst case, a user enables the automatic deletion of unused point sources and loses unused point sources that they still wanted, even though point sources are not that important anymore.

    Please make PointDb_RemoveEmptySource visible by default so…

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  4. Expose connection history information to PI SMT

    As PI System administrator, I would like to know the number of clients connection given a time frame. (e.g. * -1 month) Currently, this is only exposed to the pidiag command line utility. It would help me as a pi system admin to see it within a user interface such as in PI System Management Tool.

    Also please expose this command to PowerShell Tools for PI System as well for better manageability.

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  5. PI SMT - Archive Editor Improvements

    Why is the second server of all selected servers the default selected server for the archive editor? (C# index 1 instead of 0?)

    If I leave the Tagname empty and press the search button the tag search dialog opens fine.
    But if I enter some text at Tagname and then immediately remove the text again and now press the search button an error message "Error -2147220305: Empty strings not allowed. (Check Tagname)" appears even twice in a row.

    If I enter a tagname that does not exist an the error message appears that is ok, but it also appears twice…

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow PIWorld and piusers to be deleted

    Nobody should be using the "PIWorld" PI Identity or the "piusers" PI Group. The most that we can do at the moment is disable them. It would be much better if we can just delete them and never look back.

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add ability to honor archive list file locations when adding new server to PI HA Collective

    When adding a new server to a PI HA Collective, all archive files selected to be included in the initialization are copied and registered with the new server in one defined location in collective manager.  This can create more manual work for organizations who wish to have all servers have similar file structures.  If the primary server has archive files registered across multiple locations, these locations should be honored and attempt to move files to these locations first, then if a drive is not available fall back to the default location.

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  8. Easy selection of PI Archives to Backup

    Currently, if we want to do a backup of an archive in SMT, we have to tick it. But the customer may has like 500 archives and wants to copy 100 of them. There is currently no friendly-user way to select multiple archives (without unregister them) using strg or shift key (like selecting multiple file on windows)

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  9. Be able to change "State number" in SMT Digital States.

    SMT Digital States you can't change the number. This matters when trying to insert a new state. You have to rename everything to move it down. In PSE with enumeration sets you an change the number easily.

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  10. Replace the "http://techsupport.osisoft.com/" link in the "About" window of PI System Tray

    The "About" window of PI System Tray contains the link "http://techsupport.osisoft.com/". However, this link does not use HTTPS and will redirect to "https://my.osisoft.com/". Please replace the link with an appropriate one that uses HTTPS and does not redirect.

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  11. Replace "timeout parameters" with "tuning parameters" in the description of the PITUNING Database Security table

    In PI System Management Tools, under the Database Security plugin, the description of the PITUNING table is:
    "Controls access to Timeout parameters and the Firewall"

    "Timeout parameters" is the old name for "tuning parameters", I'm guessing from the days when the tuning parameters stored mostly connection timeout times. New PI administrators will not know what a timeout parameter is. Please change the description of PITUNING to:
    "Controls access to tuning parameters and the Firewall"

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  12. By default, hide the tuning parameters of legacy features

    Many tuning parameters are irrelevant for PI systems that are new or no longer use legacy features. To reduce the clutter in PI System Management Tools, the tuning parameters of legacy features should be hidden by default, just like other tuning parameters that are hidden by default, such as Base_AllowSIDLookupFailureForMapping. Tuning parameters that are hidden by default appear in PI System Management Tools only when they are set to a custom value, which appears in the Value column.

    Below is a list of tuning parameters of legacy features. These account for >10% of all tuning parameters that are visible by…

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  13. option to manually disable secondary collective member synchronization

    I have experienced several synchronization errors with data archives running on virtual machines in separate errors, generally after MS updates. Please provide a way to stop synchronization of configurations between collective members, so I can perform MS updates and reboots without fear of having to re-synchronize my secondary archives afterwards.

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  14. Increase Box Length for Tagname Field in Archive Editor

    The Tagname field visible length should be increased within Archive Editor in System Management Tools. The full tag name is limited and cannot tell what is listed because the name is cut off. (See screenshot and steps listed below.)

    Steps to reproduce:
    1. Navigate to PI System Management Tools -> Data -> Archive Editor
    2. Search for long tag name
    3. Select Multiple tags in the tag search box
    4. Click "OK" to confirm selection
    5. Select the dropdown icon within the tagname field to list all selected tag names.

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  15. Archive Editor: Preserve the selection of multiple rows when right-clicking on a cell within the selection

    Currently, if you select multiple rows in the Archive Editor and then right-click on a cell that is not the ► cell or the Value cell beside it, your selection will collapse to the row whose cell you right-clicked.

    That is, no matter how many rows you select, only 2 cells out of that selection will preserve your selection after you right-click on them.

    This is frustrating when you select multiple bad events to delete and then right-click within your selection but not on 1 of those 2 special cells, and you must select your rows all over again.

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  16. Show pending changes in the Archive Editor of PI System Management Tools

    Currently, there is no visual distinction between:
    • rows that contain no changes,
    • rows that contain unsaved changes, and
    • rows that contain saved changes that have not been processed by the PI Data Archive yet (this happens when you refresh too quickly after saving changes and the refresh does not return your changes).

    Please consider adding an extra "Changes" column that indicates what changes the user made (e.g. "Event will be deleted", "Edited value and annotations", "New event", or "Processing…"). Also consider changing the cell/row background colour, font colour, or font formatting (bold, italic, etc.) to reinforce the…

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  17. GUI to edit bitmask tuning parameters

    Currently, bitmask tuning parameters are entered and displayed as a single number. Not every PI administrator will know that a bitmask involves the addition (or "ORing") of each bit to combine their effects. It is also time-consuming and error-prone to calculate a new bitmask or interpret what an existing one means.

    Please consider creating a GUI to edit bitmask tuning parameters. A modal window that contains a check box for each bit would suffice.

    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  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
  18. Spelling mistake in Archive_AutoArchiveFileSize's description

    In the description of the tuning parameter Archive_AutoArchiveFileSize, "occurs" is misspelled as "occurrs". This misspelling is also followed by a semicolon instead of a period.

    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

    2 comments  ·  System Management  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • 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