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. 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 →
  2. 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 →
  3. 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.

    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 →
  4. 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.

    6 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →

    This is currently possible by leveraging AF. In AF, you can configure a template with the desired PI Point attribute configurations, then you can exercise the “Create or Update PI Point” option to change the PI Point attribute.

  10. 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.

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

    4 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 →
  12. 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.

    14 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. pisrvstart and pisrvstop scripts should have pilogsrvX64

    pisrvstart.bat and pisrvstop.bat scripts should have "pilogsrvX64" added to them.  Currently all services except the "PIPC Log Server x64" are started/stopped by these scripts.

    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 →

    This log service is used by 64 bit application that loads the PI API. The most common being 64 bit PI Interfaces. Therefore if you have 64 bit PI API based applications, these scripts should start/stop the service for you. Please contact tech support if you have these applications and pilogsrvx64 is not in your pisrvstart and pisrvstop scripts.

    As a side note, recent releases of the PI Server implements virtual service accounts for all the Data Archive related services so please consider it for an upgrade.

  14. PI SMT: some plugins missing features for future data

    Certain plugins in PI SMT do not have features to support future data
    1. Snapshot and Archive Statistics (is available only through piartool)
    2. Current Data does not subscribe to timeseries in Update Manager
    3. Stale and Bad tags

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

    14 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. Store thread history along with connection history in the server

    Storing the thread history(pibasess/piarchss etc) along with the connection history will help to better understand and troubleshoot issues on the archive and will serve as a kind of auditing on the behavior of connections.

    4 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. PI Data Archive - Data Share - Distributed, Scalable, Load Balanced

    OSI should get together and devise a proper data synching mechanism that should guarantee synching archives for all backfilled events and so on.

    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 →
  18. As a PI Administrator, we should be able to see which PI mapping was used for a Windows AD user in PI message logs.

    Through PI message logs I want to see which PI mapping was used for a Windows AD user, currently only the PI identity associated the windows AD is visible in the Logs. PI mapping information will give us more idea/facts about the particular Windows AD user.

    5 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 →
  19. 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 →
  20. 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".

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