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. PSE tables Cache Interval needs to allow date /timestamp for cache interval

    Enhancement Request for PSE tables "Cache Interval" to allow a date/timestamp/offset to be entered for the cache interval.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
  2. In the PI Server install kit, label deprecated components as such and state the replacement

    The PI Server install kit includes many deprecated components, namely:
    • PI Totalizer Subsystem
    • PI Alarm Subsystem
    • PI Performance Equation Scheduler
    • PI Batch Subsystem
    • PI Module Database Builder
    • AF Collective Manager

    Also, the PI AF Link Subsystem is not needed if the PI Module Database, which is deprecated, was never used.

    Please label these components appropriately and ideally also state the replacement. Otherwise, a new PI administrator might install some of these components "just in case" or follow outdated advice on how to set up a PI system without knowing that it is outdated.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →
  3. Have an option to use step interpolation to the previous event

    When the Step attribute of a PI Point is "on", PI assumes that a value is constant until the next event, which works well in most cases.

    For PI Points 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. Please add this as an interpolation option for PI Points.

    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 →
  4. Have more user-friendly names for objects, columns, and column groups

    The current names of objects, columns, and column groups usually use some combination of camel case, abbreviations, and no spaces, which makes them difficult to read. Nobody writes like this outside of programming, and most users of PI Builder are administrators, not developers.

    It's not like spaces are never used; they are just not used enough. For example, the UOMClass object has a column group called "UOM Mapping". The ElementTemplate object has a column group called "Attribute Columns".

    Please make the names more user-friendly.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Builder  ·  Flag idea as inappropriate…  ·  Admin →
  5. Expand PI Point Array DR functionality: Source Units

    Currently, the PI Point Array data reference allows the Source Units field to be set, but this setting applies to all points in the array. It would be better if the Source Units field could be set individually for each point in the array for conversion to the Default UOM.
    Use case: we have multiple PI Points we want to put into an array, but some have source units of lb/h while others have source units of klb/h. We would like to enter the source units individually so all values in the array are converted to the same UOM (klb/h).

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
  6. Event Frames that can expire/auto-delete/archive

    When generating Event Frames it would be useful to automatically remove the Event Frame, either when no longer active or in combination with no longer active and acknowledged, or other conditions.

    An example use case would be for PI Notifications - the need to retain the Event Frames might not be there once a Notification is sent and action taken.

    See https://feedback.osisoft.com/forums/555148-pi-server/suggestions/17219861-ability-to-send-a-notification-without-being-trigg

    For example, I might sent a notification to remind someone to use PI Manual Logger to enter some data, but I don't need an Event Frame to exist after this is dealt with.

    Other examples are that I…

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  7. Ability to manage non-impersonated linked tables without PI AF Server Admin privilegies

    PI AF Admin would like grant permissions for users that are not level server admins to create and edit non-impersonated linked tables. Currently this only allowed for AF server admins or using impersonated linked tables.

    User guide:

    https://livelibrary.osisoft.com/LiveLibrary/content/en/server-v12/GUID-B6374C40-8922-40CC-8E76-45CC646DA03F

    https://livelibrary.osisoft.com/LiveLibrary/content/en/server-v12/GUID-D1BDFD1B-8720-4CAD-8A06-0FCE958664BC

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  8. Create additional Limit trait attributes

    Currently there are 7 standard limits available to be used as limit traits. However there are situations where more than 7 are required. Users would like an option to create additional limit traits rather than having to manually configuring additional intervals in PI Vision multi-state.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add Process Capability Statistics fundtions (Cpk, Ppk)

    While it is possible to manually calculate Process Capability Statistics, such as Cpk and Ppk, using AF Asset Analytics, it would be much more convenient to have a built in function to calculate these values, specifically in relation to the SQC Western Electric rules analyses available in AF asset analytics already.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
  10. Web Service Configuration - Dynamic "Path" for the JSON Body

    Allow free-form JSON construction. Maybe not replace the simple JSON guide that is the only entry form now, but free-form would allow the kind of flexibility that would empower the user.

    This would allow a single template to be used, rather than the workaround to manually override the template for every individual sensor configured, resulting in hundreds of template copies in which only the "Path" field is edited

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  11. Setting to send email notification to all subscribers on one email

    I believe this has been requested before by someone but I can't find it so I am submitting a new feedback/request. It would be very useful if there was a setting for PI Notifications that would allow for sending emails to all subscribers on a notification rule in a single email instead of sending individual emails to each subscriber. For example, if there was a setting that would allow sending one email for a notification rule with all subscribers on the "TO" line that would allow users on the email notification to see who else received the alert and provide…

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  12. Enable Compression for recalculated Analyses up to "Now"

    Analysis Recalculation produces Out of Order Events, which means they are not compressed.
    The reason for this behavior is, that there is a more recent snapshot value existing. This also happens, when Recalculation is performed till "Now" (*), because the Analysis Service performs the Recalculation in chunks (see "Will PI Analysis Recalculation follow compression and exception?")

    Would it be possible to make the Analysis Service first delete the time range fully (when recalculating up to "Now") and let it perform the recalculation in chunks afterward?
    This would not produce OOO Events and compression can be applied.

    The only workaround at…

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow multiple Notification Message Formats for the same Notification

    For Notifications which send on Event Start and Event End, it would be useful to have the ability to have multiple Message Formats for the same Notification (one to send out at start, one to send out at end).

    Advantages:
    -Can include "End Time" in only the Notification sent at end (rather than showing an erroneous 1/1/1970 00:00:00 included in the Notification sent at start)
    -Can include "Duration" in only the Notification sent at end
    -Can fully customize different messages for start and end of the Event Frame

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow additional authentication types for web service delivery endpoints in PI Notifications

    Allow for additional authentication types to be added for web service delivery endpoints. Currently, the only available options are Windows, Anonymous, and Basic.

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow dots in JSON property names when using REST Delivery Endpoints

    When configuring a Noification with a REST Delivery Endpoint, there is no way to escape a dot (".") so it doesn't gets interpreted as a path delimiter. There are cases when the dot must be part of the property name. One way to solve it would be to allow escaping it with a backslash or even better (IMHO) to use the JSONPath way to solve this: being able to specify arbitrary property names putting them between brackets and single quotes: ['prop.erty'].

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  16. Improve Asset Analytics error message: "<Attribute>: Cannot convert <time> to AF time"

    The error message thrown when attempting to use a timestamp input with ValueType other than DateTime in an Asset Analytics calculation refers to "AF Time," which is unclear for many users.

    An example of when the error would be thrown is when creating an expression that uses TagVal('attr1', 'time1'), where 'time1' is a String-valued attribute.

    A better error message would read something like:

    "<Attribute>: Cannot convert <time> to ValueType DateTime"

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
  17. Improve PI Server Installation kit: disk space requirements should include the minimal PI Backup

    When calculating the disk space requirements on a recent upgrade the drive was expected to have only 138 MB installed. But the install failed due to not enough disk space on the drive because the minimal backup needed a certain amount of disk space. This need should be included in the Required Disk Space panel when upgrading.

    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 →
  18. Separate priority setting for Data Read and Data Write

    Data Read and Date Write (Buffering) from/to PI Data Archive is based on the priority settings in PI SDK and PSE. We have a architecture of 6 member PI collective and all the source data is not buffered to the individual collective. Hence for other applications like PI Analysis or any other 3rd party applications data read should from couple of collective members and data write should be to 4 collective members.
    As per the current setup, if we enable the priority for 2 members in collective, data read and write is happening only for those members (Default behavior). But…

    7 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 →
  19. PI Recalculator Subsystem Should Support Recalculation for Point Sources Other Than ‘C’

    As a PI Recalculator Subsystem end user, I need the PI Recalculator Subsystem to support recalculation of PI Performance Equation tags with point sources other than 'C'. This feature would be especially useful because of the PE Scheduler service startup performance issues associated with not assigning a unique point source to each PE Scheduler instance as described in KB00296 - Best Practice: Assigning a unique point source for each instance of an interface.

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow Asset Analytics to Evaluate functions for questionable flagged values

    Data can be flagged as questionable, which should mean the value may or may not be valid. Asset Analytics seems to be rejecting the value as Bad. The function instead should evaluate the result, but flagging the result as questionable as well.

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 47 48
  • 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/PREVIEW
COMPLETED