Users would like to be able to pull in the instrumenttag of a PI point into an attribute that is referencing it. This isn't currently possible because the AF server and any attribute aren’t aware of most properties of the PI point itself, so pulling in and making use of those fields is not an option. To some extent, the AF server is an abstraction of the PI Data Archive, and being able to determine what other source tags it is dependent on wasn’t one of the use cases that it was written for. This is particularly true for calculated data, since AF contains an Analytics engine that is intended to replace or deprecate any calculations performed directly by the data archive. would like the use case altered to allow for AF and attributes to be aware of PI tag properties.
