Jørgen Foss
My feedback
-
36 votesJørgen Foss
supported this idea
·
-
221 votes
Reopening this suggestion to collect additional feedback.
Jørgen Foss
supported this idea
·
-
24 votesJørgen Foss
supported this idea
·
-
37 votesJørgen Foss
supported this idea
·
-
18 votesJørgen Foss
supported this idea
·
-
26 votesJørgen Foss
supported this idea
·
-
149 votes
At this time, this item is not currently scheduled for a release of PI Vision. If this changes, this item will be updated to reflect the current status.
Jørgen Foss
supported this idea
·
-
5 votesJørgen Foss
supported this idea
·
-
55 votesJørgen Foss
supported this idea
·
-
70 votesJørgen Foss
supported this idea
·
-
122 votes
We are currently researching this item and evaluating it for a future release.
If you have a moment, please let us know if you have a preference for how data item descriptions should be displayed in trends. For example, would you prefer to be able to configure the trend legend to show the item’s description, that the descriptions be shown under the plot area of the trend, or would you like them to be displayed in another way?
Let us know what your preference is by adding a comment below.
Jørgen Foss
supported this idea
·
-
177 votes
At this time, this item is not currently scheduled for a release of PI Vision. If this changes, this item will be updated to reflect the current status.
Jørgen Foss
supported this idea
·
-
224 votes
We are currently working on providing the ability to add multiple cursors to a trend for the PI Vision 2019 release.
UPDATE: It will be possible to add multiple cursors to trends on displays as well as popup trends and to the trend in the new ad hoc workspace that is being introduced in PI Vision 2019.
Jørgen Foss
supported this idea
·
-
234 votes
Ad hoc trending is a feature that is in development for the upcoming release of PI Vision 2019. This feature will support selecting data from displays to add to an ad hoc trending workspace for analyzing data and investigating issues on the fly.
Jørgen Foss
supported this idea
·
-
256 votes
We are currently researching this item and evaluating it for a future release.
Jørgen Foss
supported this idea
·
-
287 votes
We are aware of the interest in this functionality but at this time it is not in our short-term plans to implement.
Jørgen Foss
supported this idea
·
-
12 votesJørgen Foss
supported this idea
·
-
49 votesJørgen Foss
supported this idea
·
-
63 votesJørgen Foss
supported this idea
·
-
72 votesRESEARCHING / EVALUATING · 22 comments · PI Server » Asset Framework (AF) · Flag idea as inappropriate… · Admin →Jørgen Foss
supported this idea
·
I find Dave Johnsen’ post excellent.
There are probably several ways to achieve “Extensible analytics”.
To give another customer’s view on this:
We use a Python Flask server hosting our Python code and a custom DR to call the functions. As Dave points out the CDR has some draw backs.
We can also call our Python Flask server using the REST possibility in Notifications but creating an event frame for each calculation is over kill.
One possible extension for Osisoft that would be more generic is to let the analysis service be able to send web requests with a setup much like the one in Notifications, but where the trigger is the same as a built-in analysis. Then it would be up to the hosting server to able to handle the web requests. The hosted functions could essentially do all that is needed i.e. retrieving data from PI and writing data back to PI. If a response to an attribute is required, then Osisoft should define the response format. (Mathworks or other calculation server providers would have to adapt the Osisoft format)