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. Thorough Analysis service message logs

    Having more thorough and detailed messages for the Analysis service in the event logs, especially upon startup.

    Environment details + Language settings that the Analysis service is using should be mentioned in the startup logs in order to better troubleshoot configuration issues without needing to go through a trial and error process.

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. AF Function Call to test for existence of a PI tag

    Some Analytics fail due to a tag not existing. It is possible to test for a Bad value via the BadVal() function, however, this does not work if the tag does not exist. Consequently the equation will not run. This caused me many hours of debugging when trying to identify why several calculations were not running out of many 1000s which were defined for the AF template.

    It would be useful to have an AF function that explicitly tested for the existence of a Tag. In this way calculations would still run resulting in a cleaner looking summary in the…

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Recorded Values Discrete Time Weighting

    When using the recorded values function in Analysis, Time weighted totals and averages assumes that the data is continuous and not discrete. This creates issues with data streams that are both discrete and require time weighting functions. Ideally a third calculation type needs to be added to Total, AVG and the like which is Time Weighted Discrete. This will adress this issue as is currently done in TagTot or TagAvg.

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. multiple instancnes of analysis service

    As a PI administrator I would like to be able to create multiple instances of "PI Analysis Service" windows service for these reasons:
    - avoid new potentially problematic analysis from affecting the ones that are operational and working correctly by setting one production instance and one test instance for example.
    - every instance could have its own log files and we could move some analyses to a new instance to troubleshoot them
    - make possible to distribute the resources usage for asset analytics on more than one server

    The idea was already declined in "https://feedback.osisoft.com/forums/555148-pi-server/suggestions/33839161-multiple-instances-for-asset-analytics" nevertheless i think…

    16 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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Additional capabilities for rollup analyses

    I find myself making analytics on child elements which by themselves have limited value, but are needed to get rollup analyses to work. This adds complexity to the design of AF. Two ideas would improve this:

    1) Count # of attributes that meet a certain criteria. For example, you want to count the number of active HIHI or LOLO alarms on child elements at a given time, so you'd have a rollup analyses that counts how many attributes 'Alarm Level' equals "HIHI" or "LOLO"

    2) Additional attribute filtering, such as AND/OR logic. Continuing with the example above, let's say you…

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Allow event scheduling for PI Point DR attributes that use RelativeTime or TimeRange

    Currently it's not possible to use attributes that are based on a PI Point Data Reference with RelativeTime or TimeRange settings as triggers for analyses with event-triggered scheduling. You get the "No valid triggering inputs found" error. The reason is that this kind of configuration does not support AFDataPipe, as detailed in the first table in "Restrictions on viewing time series data".

    https://docs.osisoft.com/bundle/pi-server/page/restrictions-on-viewing-time-series-data.html

    A workaround is to create a second attribute which simply refers the same PI Point without any RelativeTime setting, and to include that in the analysis expression unobtrusively, e.g. by multiplying with 0 and adding it to…

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Allow Asset Analytics to output to annotations

    As someone who has migrated our calculations from PI ACE to Asset Analytics, we need to be able to annotate various calculation outputs in the same way we were able to with PI ACE. Please enable analyses to output annotations to various PI Tags in a similar fashion to how PI ACE allowed this.

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Add a string array function to extract all items into a string result

    Our process is writing an array of strings into an AF attribute of the same type. This AF attribute may receive information of different size (index) in time.
    We need to extract all the information contained in the string array (all the items) and store it in a PI tag of type string so it can be viewed in PI Vision or any other client.
    Since there is no For-Loop function in ABA, we need a new array operation (for example GetStringContent()) to based on an event or periodically store this complete string in a PI tag.

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Improve usability of TagNum function

    The TagNum function seems to be the only function that requires a double quote as opposed to single quotes.
    Many other TagXXX functions call for single quotes for its attribute or PI Point arguments.

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Translate the descriptions of functions in PI System Explorer

    See the attached picture. The picture also reveals other parts of PI System Explorer that are not translated. The picture and the idea for this suggestion come from https://pisquare.osisoft.com/s/feed/0D58W00006XNrBuSAL.

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Function to extract Data Reference Type

    We would like to be able to extract the data reference type (PI Point, None, Formula, Table Lookup, etc.) for an attribute using PI Analysis, similar to the TagType function for PI points.

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Abililty to minimise Preview result window

    When you develop an expression it is very useful to use the preview function. Quite often you can discover and debug directly from this, but you are not abel to close down the window and check the code!
    So either you memorise or you export the csv file ... which is quite cumbersom.
    I suggest that you are allowed to minimse the preview window to revise your code so you can easily crosschek your findings. This small change would speed up development .

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Provide 'GoTo' like Funciton

    Please provide a 'GoTo' like Funciton for Analysis Expressions to skip expressions or maybe even go back to a previous Expression.
    I realize you don't have line numbers per se, but if the Expressions operate in order, could you use the Variable Name?
    This would be extremely useful for skipping a block of code under certain scenarios where it's just too difficult for a mile long nested if/then.
    @ Kevin G., don't decline this, vote for it ;)

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Trilinear Interpolation

    The ability to utilize three columns as input for interpolation from an AF Lookup Table to determine the result for a fourth column could be beneficial for predictions and analysis.

    Currently, only linear and bilinear interpolation is possible from an AF Table Lookup.

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. PSE Analysis Preview Results to indicate the origin of the event times

    In PI System Explorer, when using the Preview Results function for analyses, I want the dialog to indicate which of the input attributes the current timestamp originates from.

    Example: Two inputs with update frequency 1 min, Input1 without offset and Input2 with offset 00:00:30. In my Preview Results dialog I will see timestamps 12:00:00, 12:00:30, 12:01:00, 12:01:30, etc. for an analysis triggering from these two inputs. When hovering the generated timestamp I want to see if this originates from Input1 or Input2 (or both).

    This is, of course, a simplified example, but in the real world I would typically have…

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Extension of Rollup Scope without Excessive Computational Cost

    If something I'll call lists are implemented following the model of categories (that is an element can belong to multiple, arbitrarily named entities) and rollup is extended to allow that as an option in addition to the parent element, this would allow many level rollup without the cost of recursion/tree-walking. A simple utility for list maintenance could be built that could do the recursion if that is viewed to be useful since performance would not be a problem for a one-off operation.

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Check box option at attributes to handle PI tags that are bad and questionable

    This suggestion is on how you manage the input tags into calculation that at some point it returned bad value (like I/O Timeout, Bad Input, Snapfix, etc...) or became questionable. These tags will make your calc at analysis become "Calc Failed". I know that we can use Exit() or NoOutput() function but it's impractical to do this again and again in each statement.

    Generally "Calc Failed" can be caused by 2 reason, either the tag is bad or the calc itself cause error. But at least on the PI tags error we can handle at attributes level, and would be…

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Change the default triggering for Analytics from Any Inputs

    Leaving the default to Any Inputs for expression analytics can cause some performance issue as a calculation could end up triggering multiple times per second if there are several inputs. Since this is the default, some users may not take the time to evaluate the performance impacts and will leave it to that default configuration. Users should be required to select the input(s) they want for triggering before being able to save the analytics, or at least be warned that Any Inputs could be too expensive.

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Prioritize Recalculation of Analyses acting as Inputs into other Analyses (Daisy Chains)

    During bulk recalculation or backfill, enhance the PI Asset Analytics engine to prioritize the calculation of analyses that act as inputs into higher level "daisy" chain analyses. This would address performance issues at large scale, as described in Known Issue "Autobackfilling or recalculating a large number of analyses with dependencies can be slow"

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Improve Scalability of PI Analytics

    Currently you can only run a single PI Analytics instance at a time. We have two VMs running PI Analytics in a failover situation, but this means that one of the VMs is sitting idle 99% of the time.

    We are starting to hit the limits of scaling with analytics falling behind. Ideally, the analytics should be able to run on multiple VMs.

    For example, if you have 10 AF Databases and 2 Analytics servers, it should run the analytics for 5 of the databases on each VM. In a failover situation it could send the Analytics for all 10…

    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  ·  Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 9 10
  • 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