Dan.Louchbaum
My feedback
-
4 votesDan.Louchbaum
shared this idea
·
-
3 votesDan.Louchbaum
shared this idea
·
-
2 votesDan.Louchbaum
supported this idea
·
-
313 votes
We are aware of the interest in this functionality but at this time it is not in our short-term plans to implement.
Dan.Louchbaum
supported this idea
·
-
313 votes
We have started working on this feature that will allow users to define calculations on the fly in PI Vision.
We’d like to learn more from you about what you’d expect when it comes to these types of ad hoc calculations in PI Vision. If you have a few minutes, please consider taking this quick survey:
https://osisoft.az1.qualtrics.com/jfe/form/SV_0cTRDc7PCTjYNrnYour feedback will help determine how this functionality is implemented.
Thank you!
Dan.Louchbaum
supported this idea
·
-
23 votesDan.Louchbaum
supported this idea
·
-
8 votesDan.Louchbaum
commented
For Hi Speed connectors on manufacturing network, but PI DA on Enterprise network, significant traffic routes through the firewall. Compression helps the data recorded but not the traffic, which is why Exception is very important.
Dan.Louchbaum
supported this idea
·
-
175 votes
We plan to provide users the ability to pick their tag naming convention and not worry about managing a cache file. We are working on implementing this functionality with PI Connector for OPC UA.
Dan.Louchbaum
supported this idea
·
-
6 votesDan.Louchbaum
supported this idea
·
-
55 votesDan.Louchbaum
commented
Delta in value and delta in time between the exact cursor locations too!
Dan.Louchbaum
supported this idea
·
-
4 votesDan.Louchbaum
commented
On a related note I have a similar situation that could take advantage of this. I intentionally create 3 of my 15 tags in an element separately (in Builder) due to custom pi point parameters that were harder to code in AF dynamically. I have tag creation disabled in AF on these 3, which used to work fine when creating new elements in PI Builder, however in the newer version of AF the PI Builder gives an error for those 3. Case # 891201 I would like to set a special scenario to either ignore this type of error in PI Builder, but display other messages, or like you mention above, have a special option within AF that won't update any of these 3 tags, therefor the error would never need to present itself in Builder.
Dan.Louchbaum
supported this idea
·
-
102 votes
AdminAmit Dutta
(Admin, OSIsoft)
responded
We are aware of the interest in this functionality but at this time it is not in our short-term plans to implement.
Dan.Louchbaum
commented
Yes, this feature was lost from 2015 going to 2016. I believe this is also explained in this case: https://feedback.osisoft.com/forums/320517-pi-coresight/suggestions/18408949-coresight-2015r2-trend-behavior
Dan.Louchbaum
supported this idea
·
-
44 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.
Dan.Louchbaum
supported this idea
·
-
8 votesDan.Louchbaum
supported this idea
·
-
28 votesDan.Louchbaum
commented
Having two (or more) trends in a display already has the scroll bar moving in both. It definitely makes sense to also have other symbols follow along with the ride! We have users at one of our mills that thought that this was the case, but we had to explain that the value was a different time stamp, so would be good to align all the symbols.
Dan.Louchbaum
supported this idea
·
-
10 votesDan.Louchbaum
supported this idea
·
-
26 votesDan.Louchbaum
supported this idea
·
-
10 votesDan.Louchbaum
supported this idea
·
-
5 votesDan.Louchbaum
shared this idea
·
Managing across a large corporation with lots of plants. This will be a great benefit to central administration to keep standard.