1. PI Vision Profile Monitoring along height of equipment - This one is a bit tricky. For clarity, let's use an example: say you take three temperature measurements of a column, one at the bottom, middle, and top. Most often, I've seen that these three measurements are captured by three separate PI Points and the relative location of the instruments (bottom, middle, or top) is dictated somewhere in the PI Point name or PI Point description. We can easily create a graphic in PI Vision of the column we're working with and overlay trends at the relative locations in the graphic for each measurement. We can also easily overlay all of the traces on one trend for comparison. If we want to graph these values versus height from the bottom of the column it becomes tricky. This is because we can't easily pull the information around where the actual instrument sits in the equipment - as I mentioned, I've seen this most often stored in plain text in the tag name or description. There might be a workaround we could come up with depending on your specific use case if you need to look at this in real-time, but it sounds like it might be easier to use a tool like PI Datalink where you have the ability to manipulate the data a bit more. Let me know what you think, I'm curious.
2. Pump Curve - Pump curves are definitely possible using the XY Plot, you can reference this KB for more information on how you can do this.
3. PI Point Array Data Reference and PI Vision - These can't be read by PI Vision at this time.
Let me know if you have any questions or would like clarification on anything above.
We plan to define two child attribute for each measurement in a section to input Pi tags name and the physical dimension example height or section number. The total sections is also an attribute which user can define. I hope use of arrays [to hold Pi tags and their physical dimension] can be explored to develop this functionality and transfer to Pi Vision. This can have multiple uses.
I see, yes that could work. In regards to developing further functionality for PI Vision to support arrays in this capacity, we have this UserVoice item:
I would encourage you to upvote this request and add a comment if the use case differs from what was already commented by ZachOG.