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. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. 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 VT_CY. The VT_CY type is intended to represent monetary values. A VT_CY 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 VT_CY value to string, the string…

    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 →
  11. 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 →
  12. 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 →
  13. 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.

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

  17. Ability to convert historical tags to future data tags

    As a production supervisor, I would like to be able to convert historical data tags to future data tags so that I can more efficiently transition my production target tags from being something that I have to update every day, to something that I can update ahead of time. Currently my production target tags are historical data tags, meaning that I have to go in every morning and update the tag with today's production target. I'll be upgrading my PI Server soon, which will allow me to use the future data feature. If I could make these tags into future…

    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 →
  18. 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 →
  19. Auto-balance archive files

    The disadvantage of fixed archives is that they cannot grow or shrink. The disadvantage of dynamic archives is that they can potentially grow too much. Merging of small archives and splitting of large archives must be done manually.

    To solve this problem, consider making all archives dynamic, but allow the user to specify an acceptable size range for the archive files. If archive files fall out of that range, they can be split or merged automatically.

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