Ideas

PI DA Server should allow for more flexibility in terms of the format of archived data. A big advantage would be if PI could archive two timestamps per event. One timestamp will come from whatever the data source is (PI Interfaces, fiels devices, ...

It would be nice to have threshold attributes for pi points. Then we could configure that values received from the source outside this limits would be ignored (not stored), substituted by the respective threshold value or even by an "Over\Under Ra...

For users who are performing installations through the use of PI System installation kits they would like the ability to resize the Installation Complete (Installation Error) Window so that they can get all of the details on all of the modules of ...

While the recovery mechanism for queue corruption is much more robust on newer version of PI Data Archive compared to previous versions, there are still few cases where PI Data Archive does not fully recover from ungraceful shutdowns. PI Server sh...

Background: On a Data Archive where many points have been deleted, there will be many unused record numbers. Since the size of an archive file is tied to the highest existing record number (for performance reasons), this can result in archive file...

Allow the creation of tag name aliases.  This would allow us to present more user friendly option for tag name searches.  It would also help present a standardized tag name to users for tags from sources that don't follow our standard ta...

It would be interesting to have a GUI, maybe inside PI SMT, that would allow users to configure their PIBackups directly without having to mess around in 2-3 batch files. Checkboxes for the most common options, Active/inactive box etc. You could...

Normally our TAGs are filled with data coming from an analysis (or PI-Equation) by snapshot-data or recalculated data. But sometimes we have to do manual corrections due to data loss and have to write data to this PI-TAGs manually. And we are not ...

As a PI Administrator, currently there is no way to compress or average (then delete) your data automatically after an event reaches a certain age. It would be nice to have the ability to automatically compress or average specific tags after the e...

Currently, the Data Archive stores the timestamp of an event as well as it's value. It would be useful to also store the timestamp at which the event arrives at the Data Archive (perhaps this could be a configurable option set for individual tags)...