Asset-based (AF) Calculations
Expand the tag based PI Vision Calculations introduced in PI Vision 2020 to support simple AF attribute based calculations (addition, subtraction, etc.).
PI Vision 2021 introduces new capabilities that allow users to create asset-based calculations on the fly within PI Vision displays.
See an overview of new PI Vision 2021 capabilities on our YouTube learning channel: https://youtu.be/LomuqXKEH7w
For additional information on PI Vision 2021, please see the release announcement here:
Hello, guys, just for keep in history request for improve pi vision functionality - it will be nice to see hierarchy of AF for element - like an example - i want to know who is parent for displaying element without adding this info to attribute of element
PI Vision 2020 has added a rather useful feature - ad hoc calculations - except, it does not support AF Attributes as inputs. Why, oh, why not?
The whole idea is to leverage the AF tree context in all reports and real-time displays? I thought the whole OI drive has been to add context to senseless flat lists of PI Points? Now, OSIsoft comes and shoots that idea through the head where ad hoc calculations in PI Vision are concerned.
Matthew Kirkman commented
As all the customers I am involved in exclusive,y use AF in PI Vision, I had assumed the calculations in PI Vision 2020 would be AF based.
This is a very significant idea for users at Devon Energy. We only use Asset Framework in PI Vision (no tags) and there are a number of situations where a user would want to look at ratios or differences. For example- we would frequently look at things such as the difference in 2 pressures for surface equipment that is configured in line- e.g. Separator Pressure-Wellhead Pressure . When an operator or engineer is trying to troubleshoot a situation, the ability to calculate these values ad hoc would save time and effort and would eliminate the need for a calculation in AF Analytics that may not be needed again.
In addition to the calculation we would like to be able to multi-state on the result.
yes, this is what we actually hoped for when we read the 2020 release nodes. Besides we would have liked a more intuitive way of creating calculations. I really don't say that very often - but in this case you could have a look at the calculation integration of AspenTechs ProcessExplorer. There you can just configure a calculation in the Tagname field instead of the creation of a dedicated calculation object.