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. Dynamic digital state sets

    Currently, the values of string tags are stored in full for each event, which is a waste of space for string tags that have the same values appearing frequently. To save space, a digital tag can be used instead. However, to create this tag's digital state set, we must know ahead of time all possible strings that the tag may store, and this may not be possible or feasible.

    My suggestion is to introduce dynamic digital state sets. That is, tags using dynamic digital state sets would receive strings from the data source. If the string is not already part…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  2. smarter calculation of PI Backup required free space

    When backfilling tags from AF its very easy to update many archives. I would like the backup script to only require free space for archives that don't exist in the target folder. We have periodic incremental backup failures do to a lack of free disk space, even though almost all of the archives being backuped up will replace files that already exist in the target folder

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add point Type INT64, UINT64, to PI Archive

    Some interfaces such as PI Modbus allow the polling of a 64-bit signed integer value or a 64-bit unsigned integer value. Yet the database does not allow you to store these values in their native formats. You must store them as a 64-bit floating point but some precision is lost. Please add the ability to store these values in their native format.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  4. Event mode that applies NoReplace to snapshot as well

    Currently the NoReplace event mode will Append data if a value with the same timestamp as the snapshot comes in. Customer would like an event mode that would discard the value if there is existing data with the same timestamp regardless of the value for both archive data and snapshots.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  5. Provide the user ability to select Event Frame templates during the Batch to Event Frames Migration

    During the Batch to Event Frames Migration, all migrated Event Frames are created with 'Migrated' templates (i.e. PIBatchMigrated, PIUnitBatchMigrated, etc.). I would like the ability to pick and choose what templates migrated Event Frames are created with.

    As some background, Batch Interfaces currently use a standard set of EF Templates -- 'Procedure' template for the top level Event Frame, 'UnitProcedure' template for the first child level, etc. I would like to assign these default templates to Event Frames created by the migration process. This will ensure perfect continuity between migrated Event Frames and future Event Frames created by any Batch…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  6. Extract events from buffer queue files or offline archives

    Currently, the procedure to recover buffer queue files consists of parsing the queue file into a temporary archive and then merging this archive with the registered archive files that overlap with the impacted period.
    This final merge requires to take the registered archive offline, which risks dataloss if new data arrives for the period of this archive. Alternatively, the archive subsystem can be stopped to prevent this dataloss, but this will impact users and calculations that need archive data, which in turn leads to incorrect data or inconsistencies.
    Additionally, in the case of collectives, this needs to be repeated for…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  7. Ability to store metadata information for PI data

    For forecasts, probabilities are assigned to each forecast data. It would be helpful to be able to store this information (metadata) for each forecast value.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  8. Have the ability to change PI Message log file configuration (Size, Duration etc)

    If verbose logging is setup for applications such as (PI Batch) which write to the PI message log (or if you have very busy PI servers with lots of logs), the file sizes can get to several GB in size. It would be good to have the ability to configure the log file size

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  9. Digital State Sets and Bit Flags

    a common data type encountered are Double Integers as bit flags, where different combinations of each bit of the binary representation of the double integer corresponds to a state. PI's Digital State Sets do not handle these well.

    First, it requires that even unused states are created in the set . . . annoying, but not a total hindrance (there is another idea posted pertaining to this particularly)

    Second, digital state sets have a maximum of 16383, which is only 14 bits, which is only sufficient for single integer (8 bit) flagging techniques.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  10. Provide the capability to apply compression on uncompressed data, aka recompress using offline archive utility.  See work item 6944OSI8.

    Provide the capability to apply compression on uncompressed data, aka recompress using offline archive utility.  See work item 6944OSI8.

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  11. 2 factor authentication

    As a user, I would like PI Data Archive to provide 2 factor authentication.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  12. Ability to Identify Critical (e.g. GxP) PI Tag in SMT

    A checkbox or some mechanism to identify Critical data point (e.g GxP) in SMT.
    * can be used for search filter to separate critical vs. non-critical data (gxp vs non-gxp)
    * possible additional layer of confirmation/prompt prior deletion (?)
     
    Current workarounds :
    using prefix/suffix to flag critical data point,using point source to separate,creating logical categories in AF, etc.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  13. Ability to view Instrument Tag and Point Source attributes within PI SMT > Data > Current Values pane

    Feature request would be to include Instrument Tag and Point Source attributes to be view-able through the Data > Current Values pane of PI SMT.  This would allow administrators and users the ability to quickly diagnose and/or trace PI Points from a centralized location.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  14. Incremental backups are not possible because of frequent backfilling

    Occasional back filling of data would cause 5 TB of archives to be backed up with incremental backups. This is frustrating because only a few KB of data is changed in each archive. Can OSIsoft provide a way to backup only the data that has changed or support a 3rd party backup solution that would backup only the differences?

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  15. PI Archive ability to recover from drive disconnect

    With everyone having virtual servers these days the host VM and SAN storage are on separate devices. When the storage device is unavailable or disconnected even briefly, the PI Archive process errors and gets DISABLED and can ONLY be restarted by a manual restart of the PI Archive Subsystem. You will see Snapshot updates since the VM is still running fine, but nothing gets into or out of the Archives.

    The requested enhancement is for the Archive Subsystem to be able to recover from this situation on its own.

    Here is the error message you will get when this happens…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    ANSWERED  ·  1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  17. Buffer subsystem to handle deleted values

    Can buffer subsystem be enhanced to manage value deletions from tags? We have a collective and utilize buffering to send data to both collective members however we have to jump through hoops to delete data from both collective members. It would be nice if the buffer subsystem could handle value deletions just like how it handles all other value adds and replacements.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  18. PI Archive File header should keep track of last modified recno

    The PI Archive File should keep track of the last modified RecNo. This would make cases where historical archive last modified times are updated (and potentially causing large backups) much easier to track down.

    In particular, this feature combined with the new Snapshot_TracePointID tuning parameter in PI Data Archive 2017+ would make figuring out what is updating archive last modified times much more straightforward.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  19. Support User Information in Connection History Tool

    (pidiag -connectionhistory)

    Support the collection and retrieval of PI / Windows user information by the connection history database.  

    Currently, the connection history database only stores IP addresses which can be misleading when multiple multiple users work from the same computer.

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  20. Undelete PI tags

    Recovering a PI tag that was deleted accidently is extremly annoying.
    Why do I have to create a new tag and reprocess all historical archives to convert the old tag to the new tag in the archives? (https://techsupport.osisoft.com/Troubleshooting/KB/2651OSI8/)

    It should be quite easy to just recreate the original tag if you have the pointid and recno. Maybe when deleting a tag you should only mark the tag as deleted instead of removing it from the pi point table.

    34 votes

    We're glad you're here

    Please sign in to leave feedback

    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
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED