Dan.Louchbaum
My feedback
-
356 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
·
An error occurred while saving the comment -
29 votes
An error occurred while saving the comment Dan.Louchbaum
commented
Should be managed by site PI Admins who know their own users and needs of either really tight resolution data (high speed manufacturing) or slower moving process. in the case of high speed manufacturing accidentally clicking on the default 1 Month button makes you wait a long time. They would rather have more options in the smaller seconds ranges.
Dan.Louchbaum
supported this idea
·
-
37 votes
An error occurred while saving the comment Dan.Louchbaum
commented
My OSI EA contacts have suggested that I use an AF table to manage mappings from a PI Connector array locations and the actual AF element attributes. So far this idea is working well, except for the fact that I have thousands of variables to keep mapped. Rolling out my AF to the rest of the facility will be ten's of thousands of mapping. Any time I need to "tweak" some mappings, add, remove, or even shift up or down variables (similar to managing PIPoints in SMT) I find it to be a less-than-ideal management step to have to manually "copy" "Paste" rows. Things could get mapped incorrectly on accident quite easily.
Ideal state is to allow PIBuilder to manage the table exactly like we manage tags. Then we can use Excel tricks to build out AF elements and the table all at the same time.
Dan.Louchbaum
supported this idea
·
-
4 votesDan.Louchbaum
shared this idea
·
-
5 votesDan.Louchbaum
shared this idea
·
-
10 votesDan.Louchbaum
supported this idea
·
-
378 votes
In the upcoming PI Vision 2020 release, this functionality is being added that will allow for creating calculations on the fly within PI Vision.
Dan.Louchbaum
supported this idea
·
-
28 votes
An error occurred while saving the comment Dan.Louchbaum
commented
Managing across a large corporation with lots of plants. This will be a great benefit to central administration to keep standard.
Dan.Louchbaum
supported this idea
·
-
13 votes
An error occurred while saving the comment Dan.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
·
-
202 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
·
-
67 votes
An error occurred while saving the comment Dan.Louchbaum
commented
Delta in value and delta in time between the exact cursor locations too!
Dan.Louchbaum
supported this idea
·
-
4 votes
An error occurred while saving the comment Dan.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
·
-
119 votes
We are aware of the interest in this functionality but at this time it is not in our short-term plans to implement.
An error occurred while saving the comment 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
·
-
45 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
·
-
29 votes
An error occurred while saving the comment Dan.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
·
-
78 votesDan.Louchbaum
supported this idea
·
-
10 votesDan.Louchbaum
supported this idea
·
Getting a brand new asset installed and using AF and PIVision for most every screen except SQC screen(s), still needing Processbook thick clients on the shop floor.