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. Optimize and compress non-primary historic archive files

    Currently, the same file format is used for primary and non-primary historic archive files. This does not make much sense since the two types are used very differently.

    For the primary archive:
    • Write operations should be fast since it is collecting data in real-time
    • Read operations should be fast since the most recent data is usually the most relevant
    • File size is not a concern since there is only 1 primary archive

    For non-primary archives:
    • Write speed is not a concern since write operations are infrequent
    • Read operations should be fast because users may want…

    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

    4 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  2. Compress archives that are backed up using "Copy"

    Currently, when a "copy" backup occurs, the archives are copied as-is. Archive files take up a lot of space, but they also compress very well, and since archive backups are rarely accessed, it makes sense to trade off increased access time (due to the additional work of decompression) to get a smaller file size for the archive backups.

    The exact method of compression (new file format, put archives in a compressed folder, etc.) will be up to OSIsoft. In my testing, I used disk compression on the archive files.

    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 →
  3. Replace the batch (.bat) scripts in the %PISERVER% folder with PowerShell (.ps1) scripts

    This replacement is appropriate for several reasons:
    • PowerShell is easier to read and is a more powerful language than the batch language.
    • Batch scripts are best used in Windows, whereas PowerShell is cross-platform. This replacement will support OSIsoft's expansion outside of Windows.
    • Microsoft is pushing for PowerShell and leaving batch files in the dust. Ideally, PI systems would not rely on legacy technology.

    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

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  4. PI Data Archive Installation Wizard should provide an option to restore from a backup or copy current configuration from another PI Server

    As we enter 2020, the process of moving/restoring the PI Data Archive hasn't changed since its inception. Typical procedure to move a PI Data Archive on a new server is to install same version of software and then perform backup/restore of the old server. The process can be simplified if the installation wizard provides an option of whether this is a new installation or rebuilding of an existing server. This eliminates unnecessary install of out of the box configuration just so that the files be overwritten later. Wizard should provide options of overwriting license file, paths to archives and queues…

    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 →
  5. Allow edited default tag attributes to be used in Point Builder SMT Plugin

    Currently there is a procedure that allows using piconfig to Change Default Tag Attributes however these changes do not impact the defaults of tags created through Point Builder plugin within SMT but works on other clients that allow tag creation such as PI Builder.

    This request is to allow SMT to accept these Tag default changes to be reflected on tags created through PI SMT

    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 →
  6. Option to install sample PI tags with simulator interfaces

    Posted on behalf of a customer.

    As of PI Server 2018 SP3, simulator interfaces have been removed from the PI Server setup kit, and the default PI Points are no longer installed. These were very important to check if the server installation went well. I like to have options in the PI Data Archive install kit to install sample tags and simulator interfaces together with server component. This makes much easier to set up environment test.

    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

    0 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  7. Dictionary encoding of strings in string tags

    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, please use dictionary encoding (AKA dictionary coding or dictionary compression) to store the values of string tags. The space saved for string tags that have many repeated values should hopefully offset the extra space used for string tags that have mostly unique values.

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

    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

    3 comments  ·  Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. 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 →
  15. 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 →
  16. 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 →
  17. 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.

    26 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 →
  18. 2 factor authentication

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

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