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. 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 →
  2. 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 →
  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. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. Powershell PIArchive.Reprocess

    A powershell method for reprocessing PI Archve Files.

    $myPIArchive = Get-PIArchiveFileInfo -Connection $myPi -Name "someArchiveFile"

    $myPIArchive.ReprocessArchive -NewFileName $false|"filename" -Type Dynamic|Fixed -OtherCoolOptions

    Reading data from a reprocessed archive is significantly faster, so I am adding this as a maintenance-task currently using
    cmd /c "%PISERVER%\bin\piarcss.exe -if old -of new"
    (For some reason start-process didn't work for me)

    I would also love a $myPIArchive.LastReprocessedTime for housekeeping. I am currently storing that in a separate hashtable.

    10 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 →
  11. 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 →
  12. Make a point class similar to "base", but without zero, span, or typical value

    Most of the time, zero, span, and typical value are unused, cause confusion, and/or lead to easy but costly mistakes.

    Typical value is probably the most useless PI Point attribute. It doesn't affect the PI system. It is just there for the user's reference. Why not a range of typical values? Why not calculate it dynamically based on actual data? Typical value is superseded by limit traits in PI Asset Framework, so there is no need to force a typical value on every PI Point.

    Zero is mostly used for Float16 PI Points, which is probably rarely used these days.…

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

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  14. Interpolation options for step tags

    When the step attribute of a PI tag is "on", allow the user to specify an interpolation method.

    The current method assumes that a value is constant until the next event, which works well in most cases.

    For tags 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.

    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 →
  15. 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 →
  16. Automated re-compression/average after a period of time

    As a PI Administrator, currently there is no way to compress or average (then delete) your data automatically after an event reaches a certain age. It would be nice to have the ability to automatically compress or average specific tags after the events have existed for a certain period of times. For instance, I keep data for “Tag1” in 5 second intervals for 2 months. After 2 months, I average those events over 5 minute intervals and delete the 5-second interval data thereafter.

    4 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. Prevent PI-TAGs to be overwritten with new data for certain time range

    Normally our TAGs are filled with data coming from an analysis (or PI-Equation) by snapshot-data or recalculated data. But sometimes we have to do manual corrections due to data loss and have to write data to this PI-TAGs manually. And we are not allowed to change these corrections afterwards (e.g. when our obligatory technical account is already done).

    In this cases it would be great if I were able to configure (in AF) time ranges for PI-TAGs in which all archive data for these TAGs is locked and cannot be overwritten by other data (independent from where it comes from).

    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 →
  18. Convert incoming string data to float and provide division all in the same tag instead of a PE

    OPC server is outputting data with the currency data type (VT_CY) and it needs to be stored in the float type.  As per the OPCtoCSV document, the OPCtoCSV tool/OPC interface invokes VariantChangeType in order to convert this currency value to it's string representation before PI receives it.

    "Some OPC servers have property values that are type VTCY. The VTCY type is intended to represent monetary values. A VTCY value is a fixed-point number with four digits after an implied decimal point that is scaled and stored as a 64-bit integer. When VariantChangeType converts a VTCY value…

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