Dan.Louchbaum
My feedback
-
130 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
·
-
2 votesDan.Louchbaum
shared this idea
·
-
1 voteDan.Louchbaum
shared this idea
·
-
146 votes
An error occurred while saving the comment Dan.Louchbaum
supported this idea
·
-
59 votes
An error occurred while saving the comment Dan.Louchbaum
commented
Was informed a critical display was missing. Would love to know why. Found in Event viewer the user, display Id, and name of the display when it was created using the utility, but not when it was deleted. Doesn't make sense why that is not logged.
Dan.Louchbaum
supported this idea
·
-
39 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
·
-
53 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
·
-
7 votesDan.Louchbaum
shared this idea
·
-
10 votesDan.Louchbaum
supported this idea
·
-
88 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
·
-
16 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
·
-
6 votes1 comment · OSIsoft Cloud Services » Assets & Metadata Rules · Flag idea as inappropriate… · Admin →Dan.Louchbaum
supported this idea
·
-
86 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
·
-
163 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
·
-
48 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
·
-
97 votesDan.Louchbaum
supported this idea
·
-
5 votesDan.Louchbaum
shared this idea
·
Our elements are named by the piece of equipment that they are, not based on the process flow. Example elements: Mid-section_shaping_Motor and Final_Cutting_Motor. I want to create a Pi Vision screen that shows an attribute of these elements from left-to-right or top-to-bottom that shows process flow order. In this case, because my 'Final..' element starts with "F" which is before "M" in the alphabet it is out of order which confused my process techs using the screen. If the sort-by-attribute filter was available then I could create a new attribute managed only by Pi-admins for ordering these elements, and assign them a sequential process order WITHOUT having this number as apart of my element name. Putting the number in the beginning of the element is the current work-around suggestion. This is a bad work-around because the number should mean nothing to the end-users of PiVision. Adding to that, in some cases my element names have other numbers on purpose already. Example element might be Mid-section-7_Drive. the workaround today would tell me to put a sequential number before 'mid' that would make my new Element name like this: 83-Mid-section-7_Drive. The workaround is not worth effort and causes confusion.