Show the reference arrow on child elements of a referenced element.
When you copy an element that has child elements the reference arrow only is visible on the parent. All children look like non referenced elements. This could be confusing in a large AF tree, referenced items that do not have the arrow could be mi...
On PI System explorer when you copy an attribute with child attributes, only the first child attribute get's copied as well and the rest is missing. This was working with PI System Explorer 2016 R2 SP1 whereas it does not with Version 2018 SP3 pat...
Add IsExcluded('attribute') function to AF Analysis.
Add new isexcluded(attribute_reference) function to be able to easier distinguish between Tag/Attribute errors and excluded attributes. Currently it is quite tricky to filter if an attribute is in error due to data source error or an excluded tag....
Provide a tool (in PSE?) to assist management of analytics scheduling offsets
We recommend customers use offsets to distribute scheduled calculations across time but there is not a good way manage this.Propose some utility to list a group of all scheduled analyses by same period, users supply X number of offsets and then th...
In Asset Analytics, there isn't a way to include a filtering function in a single analytic. For example, you may be calculating run hours on a motor, but there is no way to filter the calculation so that it is only done when the motor is running.
As a process engineer I would like to be able to integrate complex specific calculations, such as from a 3rd party analytics engine, so that I can use the Asset Analytics and its context with all the available data and scheduling to run those with...
if then else in Analysis still checking/executing both parts
If then else clauses are often used for input filtering for our analysis in AF. We often face the issue that analysis cause errors although the part which should not be executed according to the condition is causing errors.Example: "if BadVal('att...
When we built complex analysis and evaluate in PI System explorer we get general error messages without any information where the error occurs. This makes troubleshooting painful. Adding row/variable information would already help a lot!