PI Server

Welcome to the PI Server feature suggestion box. We created this forum to hear your ideas, suggestions and feedback.

Please suggest your most important features and design change ideas on this site! Also vote for your favorite features now! We welcome your feedback.

  • NOTE: for bugs, please report to OSIsoft Tech Support at techsupport@osisoft.com rather than entering them on this site.

How can we improve the PI Server?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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…

    6 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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.

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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".

    5 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  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.

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

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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…

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  14. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  15. Archive Reprocessing Backup

    The current automated Archive reprocessing creates a backup of the original archive in the archive directory. This can lead to a situation where the archive drive runs out of space.

    It would be useful to be able to configure the backup location for the reprocessed archives. This should be a tuning parameter.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add a Confirmed Write methods

    All methods exposed through AF SDK and other Developer Technologies are "fire and forget". Please add methods, at least for time series data, which return when the data has been processed.

    A write operation that returns when data has been processed allows to postpone dependent operations until the acknowledgement is received. A client application using a Confirmed Write needs to handle failures and a Confirmed Write requires an active communication channel. For this reason the implementation should be un-buffered.

    Offer Confirmed Write methods through AF SDK and later with other dependent Developer Technologies.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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).

    5 votes
    Sign in
    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?

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

    39 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  19. 1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  20. Association of Multiple Tags That Represent Same Measurement

    As a PI admin, I would like to associate mutiple tags together that represent the same measurement at different time periods SO THAT users see one set of data together instead of the old data in the old tag and the new data in the new tag after DCS/PLC upgrades and platform changes are made that drive new tag naming conventions.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base