Data Archive

In the event of all the threads being consumed on a PI server a PI admin is unable to manage a PI server remotely. They must remote into the server and manage it from there. However, even from the server there are times where simple tasks like ope...

Currently, PI SMT will only allow archives to be reprocessed according to it's original type. User would like to be able to choose whether to reprocess the archives from fixed to dynamic or vice versa.

With everyone having virtual servers these days the host VM and SAN storage are on separate devices. When the storage device is unavailable or disconnected even briefly, the PI Archive process errors and gets DISABLED and can ONLY be restarted by ...

As a customer who is moving their PI Data Archive historic data to a Centralized IT Facility, hosting another PI Data Archive, and that would like to import tags and historic data from another PI Data Archive, it would be great to have a functiona...

Hello, About the tuning parameter pointDB_RemoveEmptySource the following Article : https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=KB01008 Indicates : Perform any of the following actions to trigger removal of empty point sou...

As a user I want to be able to collect, store and analyze quality information associated with real-time events and assets. This feature will allow the user to determine the trustworthiness of the data when decisions are made. Note: This was previ...

PI Archive Subsystem should be able to use operating memory more efficiently. For example by loading as many non-primary archives into its process memory as possible (perhaps it could be affected by a user setting).

Have a way to assess the data integrity so end users can trust the data and issues can be fixed quickly.

All methods exposed through AF SDK and other Developer Technologies are "fire and forget". Please add methods, at least for time series data, which return when the data has been processed. A write operation that returns when data has been process...

Currently, if you want to store predictions for 1 day, 2 days, 3 days, etc. into the future, you must create a different PI tag for each distance into the future. Future data tags should support 2 timestamps: the timestamp that the predicted valu...