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. Publish metrics

    Create standing metrics for the PI System, especially the PI Data Archive

    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. Wave Form Data Collection

    A few customers would like the capability of storing vibration wave form data in PI. They often measure data in MHz and GHz frequencies, which are at a finer resolution that the PI Data Archive is capable of storing. The wave forms are captured over periods from 2 to 30 seconds and only saved if there is an interesting event.

    Customers in data centers are also requesting power quality wave form storage in PI.

    1 vote
    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. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. Store PI Data Archive information in an SQL Server database

    Most of the PI Data Archive information that is accessible from PI System Management tools is perfect for a relational database: PI Identities, PI Mappings, PI Point attributes, PI Message Logs, etc.

    Moving all of this to an SQL Server database would make it easier for the PI Data Archive to communicate with:
    • PI Asset Framework (which already uses SQL Server),
    • PI OLEDB Enterprise (currently responsible for translating SQL queries to native PI requests),
    • PI Builder (translates the PI file format to a relational database format anyways), and, most importantly,
    • the user (users know relational databases,…

    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 →
  11. Support different data retention policies

    As an administrator, I need to ability to configure the life span of my PI data, so that data are kept or deleted accordingly. For example, data that should be deleted based on corporate mandates and data that should be kept forever are handled accordingly.

    Note: This was previously Enhancement 25774OSI8.

    59 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. 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 →
  13. Make it easier to get a list of buffered or unbuffered points on the PI Data Archive

    For PI System Administrators, it would be nice to be able to easily get a list of all buffered or unbuffered points on the PI Data Archive.

    Currently, a list of buffered points is possible to retrieve using 'piartool -bfs <id> -ptlist', but a comprehensive list would require iterating through all of the buffered sources.

    Such functionality would be nice because it would allow administrators to easily identify which data sources need to be configured for buffering, or which data sources are possibly misconfigured for buffering. It would also be a quick thing to check for points which may potentially…

    12 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. Add new PIPointAttribute for "StaleTimeout"

    While no customers have asked for this directly, I have seen many customers ask how to check a tag for being stale. The solution to date assumes all tags have the same staleness timeout, which really is not the case most of the time.

    This new "StaleTimeout" point attribute would be a duration (time span) customizable for each tag. There could also be a new PIPoint property called "IsStale" which could bounce the current value's timestamp off the "StaleTimeout".

    15 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 →

    Hi Rick,

    We are considering how to implement Data Quality in an upcoming release. A subset of that is if data is stale. If you can help us gather more customer use cases to better document the problem, and help us get a sense of how many customers would benefit from this feature, that would be extremely helpful.

    Specifically, what would be very helpful is the requirements customers have to determine when a data point is stale. We are making a serious effort to simplify the management of the PI System, so we would like to be able to avoid asking users to spend time configuring yet another parameter.

  15. Add Access Right that Allow Users to Create Tags But Not Delete Tags

    As a user of the PI Data Archive, I would like the ability to give users access to create tags but not to be able to delete tags. This way they will not be able to accidentally delete tags but they still have the ability to create tags.

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

    We’ll send you updates on this idea

    5 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  16. 64-bit Unix time

    Consider upgrading from 32-bit Unix time to 64-bit Unix time so that PI can support dates past January 19, 2038. Reasons:

    1. This date is fast approaching as a future value. It is only 20 years away.

    2. OSIsoft will need time to implement the 64-bit time stamps and convert all existing and supported PI Data Archives to use the 64-bit time stamps. At least a year of time will be used up for leeway.

    3. Once 64-bit Unix time is implemented, then OSIsoft can exclude from training presentations the (very high) upper limit of supported time. This gives the…

    12 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 →
  17. Ensure data is identical between collective members

    As a PI Administrator, I need to trust that the data is identical between my collective members. Currently, there is no way for me to be sure it is the same unless I do a side by side comparison. Data can be missing, or slightly off, and I have no easy way to understand this right now.

    26 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 →
  18. Provide more granular configuration for default ACLs

    As a PI Administrator of a PI System with complex security requirements, I need to set up different default permissions for various users so they can create tags that automatically have the proper security instead of having to rely on a process/procedure to correct security after the tags are built.

    13 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 →
  19. PI Data Archive: Improve piarchss performance

    PI Archive Subsystem should be able to use operating memory more efficiently. For example by loading as many non-primary archives into its process memory as possible (perhaps it could be affected by a user setting).

    8 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 →

    Could you please provide more details and examples of what you want to do? The Archive Subsystem already manages the files in memory, and in the file system cache. So, what are your specific situations where you see inefficient memory usage today?

  20. Reprocess fixed archives to dynamic or visa versa

    Currently, PI SMT will only allow archives to be reprocessed according to it's original type. User would like to be able to choose whether to reprocess the archives from fixed to dynamic or vice versa.

    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 →
  • 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