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. PI Archive File header should keep track of last modified recno

    The PI Archive File should keep track of the last modified RecNo. This would make cases where historical archive last modified times are updated (and potentially causing large backups) much easier to track down.

    In particular, this feature combined with the new Snapshot_TracePointID tuning parameter in PI Data Archive 2017+ would make figuring out what is updating archive last modified times much more straightforward.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support User Information in Connection History Tool

    (pidiag -connectionhistory)

    Support the collection and retrieval of PI / Windows user information by the connection history database.  

    Currently, the connection history database only stores IP addresses which can be misleading when multiple multiple users work from the same computer.

    7 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  3. Thresholds for PI Points

    It would be nice to have threshold attributes for pi points. Then we could configure that values received from the source outside this limits would be ignored (not stored), substituted by the respective threshold value or even by an "Over\Under Range" state. This discussion is pretty old in the community, and I find it quite odd this configuration was never considered (of course there could be specific reasons I am not aware of).

    The need for filtering negative values of a flow tag, for example, when summarizing data is very common.

    See this discussion below for better understanding:

    https://pisquare.osisoft.com/thread/31212-datalink-calculated-filtered-data-odd-behavior

    Users…

    6 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  4. Undelete PI tags

    Recovering a PI tag that was deleted accidently is extremly annoying.
    Why do I have to create a new tag and reprocess all historical archives to convert the old tag to the new tag in the archives? (https://techsupport.osisoft.com/Troubleshooting/KB/2651OSI8/)

    It should be quite easy to just recreate the original tag if you have the pointid and recno. Maybe when deleting a tag you should only mark the tag as deleted instead of removing it from the pi point table.

    28 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  5. New attribute for a PI point type ID

    To take full advantage of AF and substitution parameters it would be great to have a sort of type ID. Now i have to rename all tags to gain this possibility. It would be easy if i could use a portion of the tag name and a  type id. Then i could deploy AF templates with substitution parameters really fast.

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  6. Repeatedly loop future data

    Customer would like to be able to loop future data.  For instance since yearly temperatures are about the same every year for a given month, it would be nice if only one set of the projections are stored somewhere and just repeated again and again every year.

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add flag for offline archive reprocessing to honor archived digital state values

    If a tag is edited to use a new digital state set, this set will be used for all future data even though the previous state set is still used for historical data.  If a historical archive (prior to editing the digital state set used by the point) is reprocessed, the events within the archive will be coerced to the new digital state set.  This can be very confusing if the archived data is intended to be the old digital state set.

    13 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  8. Being able to activate the Log of abnormally long request made to the PI Data Archive

    It would be helpful to determine which users or applications made heavy requests to the Data Archive Server.
    This could be an option to be activated or not.
    Logging the ip, user identity, concerned tags, duration of the request
    Those information are actually available in PI SMT but there is no way of storing and analyzing them.

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  9. Link tuning parameters to the UOM database

    Many of the tuning parameters have units, but the unit can only be found in the tuning parameter's description and is not written consistently (sometimes written in full, sometimes abbreviated, sometimes written as a symbol). Linking the tuning parameters to the UOM database would clean this mess, allow the user to input tuning parameters in different units, and allow the user to convert existing tuning parameters to different units for easier interpretation.

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  10. Reduce archive file size by eliminating unused record numbers

    Background:
    On a Data Archive where many points have been deleted, there will be many unused record numbers. Since the size of an archive file is tied to the highest existing record number (for performance reasons), this can result in archive files that are much larger than necessary.

    Request:
    A method to eliminate unused record numbers, likely by modifying record numbers. As an example, three points with record numbers 1, 3, and 10 would turn into record numbers 1, 2, and 3.

    4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  11. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow bi-temporal data archiving

    PI DA Server should allow for more flexibility in terms of the format of archived data. A big advantage would be if PI could archive two timestamps per event. One timestamp will come from whatever the data source is (PI Interfaces, fiels devices, etc) - this is effectively what PI has now. In addition to that, PI Should be able to add a second timestamp recording when the event got into PI i.e. when either PI Snapshot or Archive Subsystem saw the event coming in their respective queue. Benefits and use cases:
    - any PI Client could make sure it…

    7 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  13. Increasing the dynamic range of compressed data

    I see too often customers struggling to find the right exception and compression settings. When exception/compression are not well defined, they end up having too many values or missing values, what causes a lot of problems when the affected tag is being used in other calculations (totalizations, for example).

    Consider the tag attributes " zero" and "span": today, values near the "zero" are more penalized than the values near the "span"  value, because the exception/compression deviation may be too big for the values in the lower scale of the entire tag range. It translates in poor dynamic range.

    We could…

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  14. Enhance tag search and message log filters via logical operators

    Proposed features

    - search for TAGS in PI SMT using also logical operators (like AND, OR and NOT) to refine the search criteria

    -  search for MESSAGE LOGS in PI SMT using also logical operators (like AND, OR and NOT) to refine the search criteria

    Examples

    Tag Search
    Tag Mask: *temperature* AND *pressure*

    Message Logs

    Message *10.0.0.14* OR *192.168.10.15*

    5 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  15. Backup pre-commited

    As a Pi Admin, it would be usefull to be able to locate the Precommit directory used during the PI backup process to a different location from the Backup directory

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  16. PI Server should recover from any ungraceful shutdown

    While the recovery mechanism for queue corruption is much more robust on newer version of PI Data Archive compared to previous versions, there are still few cases where PI Data Archive does not fully recover from ungraceful shutdowns. PI Server should recover from any ungraceful shutdowns

    6 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  17. Compression Standards

    The ability to define and rollout compression standards on tags across the enterprise / sites. 

    When this information is captured bottom up from sites, bad settings make it difficult to maintain a standard which inhibits cross site data comparisons.

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  18. 2 timestamps for future data tags

    Currently, if you want to store predictions for 1 day, 2 days, 3 days, etc. into the future, you must create a different PI tag for each distance into the future.

    Future data tags should support 2 timestamps: the timestamp that the predicted value applies to and the timestamp of when the prediction was made.

    The additional continuous time dimension will make it much easier to analyze the change in accuracy of prediction as the distance into the future changes.

    7 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  19. Store the timestamp an event arrives at the Data Archive, in addition to the timestamp of the event itself

    Currently, the Data Archive stores the timestamp of an event as well as it's value. It would be useful to also store the timestamp at which the event arrives at the Data Archive (perhaps this could be a configurable option set for individual tags). This would be very useful for example in situations where events are written in batches or for tracking down Out of Order events.

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  20. Force Shift warning is misleading

    When force shifting an archive, the following message is displayed:

    "Warning: This shift will clear data from the target archive. Are you sure you want to force an archive shift on <serverName> to a new archive?"

    When Auto Archive Creation is enabled (having a value in Archive_AutoArchiveFileRoot), this is very misleading. A new archive will be generated and no data will be wiped.

    This warning should only display if auto archive creation is not enabled and the archive will shift into the oldest shiftable archive.

    13 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  • 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
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED