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 https://techsupport.osisoft.com/My-Support/My-Cases/New/ rather than entering them on this site.
- NOTE: for documentation feedback and bugs, please report to Documentation@osisoft.com rather than entering them on this site.
-
Event-Weighted Summary Functions
Allow for Asset Analytics to support event-weighted summary functions (as opposed to time-weighted), such as average and count. This will allow for easily aggregating changes in digital tags, discrete sensor readings (e.g., bucket count), etc. This would allow Asset Analytics to easily perform many of the event-weighted functions of PI Totalizers.
69 votesPlanned for 2018 SP2 release.
-
Support "abstract" templates in AF
There is a need to create "abstract" element templates in AF, and this has been requested several times.
2012: https://pisquare.osisoft.com/message/4172
2014: https://pisquare.osisoft.com/message/27621#comment-27621
2017: https://pisquare.osisoft.com/thread/32721-possible-to-define-a-virtual-element-templateAn abstract class/template is one that you must create a derived version of yourself, you cannot use it directly. It's a base template, but you want to prevent users from instantiating it directly.
You might implement the general attributes for pumps as an abstract template, but you require users to create a derived template for each pump type they have, and then instantiate an element from that.
41 votesPlanned for 2018 SP2 release.
-
Conditional Exit for Analysis Expressions
Sometime you want to do an analyse only when one or more conditions are true, if the are not true you want to exit the analyse, so steps below the conditional exit are not evaluated/executed. The conditional in Analytics should look like:
if condition = true then exit analyse
At the moment this is only possible with the function NoOutput(), but then the mapped attribute should be connected to an PIPoint and you have to fill in a else condition. All rows below the conditional exit will not be executed.41 votesWe’re adding a new function, Exit(), to the library of functions.
-
Stop backfilling / recalculation of analyses
It's great that we have one more option as recalculation other than backfilling in Analyses plugin.
The backfilling / recalculation of analyses is manual process we do, because of delayed data or change of logic of analysis. In this case, sometime it happens that user has defined wrong period or selected wrong analysis while clicking on backfill / recalculate option, and if # of analysis selected are large, then it is quite frustrating to let wrong backfilling/recalculation be completed.
To stop current backfilling / recalculation operation, non-recommended approach is update the RecalculationProcessor.RequestedRecalculations.xml file. Problem with this approach is that end…
28 votesThis capability will be available in the next release.
-
Enable headers for SOAP and REST Web Service Notifications
The feature added in 2017 R2 was for authentication of the SOAP payload, not for managing headers within the payload. PI remains unusable as a secure source of data for Maximo without it because you can't configure a MAXAUTH header.
There's no way to configure headers for Notification Rules associated with a PI AF Services v2017 SP1 Elements with a SOAP or REST Web Service Endpoint. Authenticated web services, such as our company's Maximo's meter data inbound service requires a MAXAUTH header with a base64-encrypted username:password string. As a result, you can't use PI as a source of data for…
22 votesPlanned for 2018 R2 release.
-
Configurable default Attribute ConfigString
Right now, when you create an attribute in a template and assign it a Data Reference of PI Point, it defaults to a ConfigString of "\\%Server%\%Attribute%". %Server% has some known administrative headaches because what it populates as is dependent on the default server of the client tool. But in our company we are constantly switching between environments and this causes mismatches.
As recommended by OSI we have created an attribute in the root AF element called Server and gave it a string value of the name of our server. Now when we create a new attribute we map a reference…
10 votesThe upcoming AF release will allow the Server value to be defined for the AF Database as well as at the AF Server level so that all clients can treat the value the same.
Will this address your use case?
- Don't see your idea?