What the Asset Framework Needs – Timezone support
Aveva's (acquired OSIsoft) Asset Framework features attributes to specify the location of an asset. Adding a built-in timezone attribute is a missing component that would help several use cases. Many AF Servers contain elements located in different timezones.
This would allow:
- Analysis calculations to be triggered from the element's local time. This is useful when calculating calendar day calculations for the asset.
- AF Notifications from elements to contain the timestamp of the event in the element's local time. The AF Server inserts the time based on the server's local time and not the time at the asset. Users must understand this and then adjust themselves.
Adding a built-in Timezone attribute
If you are interested in learning more about the Asset Framework, here are some good places to start.
OSIsoft Blog post - Easy as PI Asset Framework
OSIsoft Youtube Learning Channel - Getting Started with the Asset Framework playlist
I couldn’t agree with this more! You need to be able to trigger based on local time of particular points and not server time. Of course, they always say you can use UTC, but that makes handling daylight savings time difficult.