Brent Bregenzer
My feedback
-
15 votes
Brent Bregenzer supported this idea ·
-
5 votes
An error occurred while saving the comment Brent Bregenzer supported this idea ·
-
4 votes
Brent Bregenzer supported this idea ·
-
2 votes
Brent Bregenzer supported this idea ·
-
10 votes
Brent Bregenzer supported this idea ·
-
2 votes
Brent Bregenzer supported this idea ·
-
5 votes
Brent Bregenzer supported this idea ·
-
2 votes
Brent Bregenzer supported this idea ·
-
7 votes
Brent Bregenzer supported this idea ·
-
13 votes
Brent Bregenzer supported this idea ·
-
3 votes
Brent Bregenzer supported this idea ·
-
3 votes
Brent Bregenzer supported this idea ·
-
25 votes
Brent Bregenzer supported this idea ·
-
0 votes
An error occurred while saving the comment Brent Bregenzer commented
@Alan.McCarthy, such functionality already exists in AF and Vision. Set up an attribute on the EF template and add the Reason trait as a Property. You can then define an enumeration set for the desired reasons and can even make this set hierarchical (i.e., a reason tree). Please see this article for more details:
https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=KB01700 -
2 votes
Brent Bregenzer supported this idea ·
-
21 votes
Brent Bregenzer supported this idea ·
-
98 votes
Brent Bregenzer supported this idea ·
-
6 votes
Brent Bregenzer supported this idea ·
-
18 votes
Brent Bregenzer supported this idea ·
-
11 votes
Brent Bregenzer supported this idea ·
Another useful option would be for the Interface to use the naming pattern specified in the EF template, similar to what the Analysis Service does.