Ideas

We are trying to standardize and mutualize all of our templates but we want to keep the security well defined : in general it work perfectly when things are in read only mode. Where write access is needed everything looks good for Elements since t...

It would be nice if there were an "Output at start" option to output values at the start of an event frame. Currently there is an "Outputs at close" option for Event Frames.

As an administrator, I need to ability to configure the life span of my PI data, so that data are kept or deleted accordingly. For example, data that should be deleted based on corporate mandates and data that should be kept forever are handled ac...

When using the Tuning Parameter, "Archive_OverwriteDataOnAutoShiftFailure", the system uses the oldest registered archive as the new primary. But it keeps the name of the old archive. It would be very helpful if the archive subsystem could rename ...

I would like to have the possibility of automatically recapturing values for event frames, so if the lab data comes in after the events are generated the late values could be recaptured automatically and in bulk. This will save the time and effort...

Recovering a PI tag that was deleted accidently is extremly annoying. Why do I have to create a new tag and reprocess all historical archives to convert the old tag to the new tag in the archives? (https://techsupport.osisoft.com/Troubleshooting/K...

Provide the capability to apply compression on uncompressed data, aka recompress using offline archive utility.  See work item 6944OSI8.

the audit record information only have the instance information, not have the interface node information. If the instance service id is the same, the audit information can't tell which interface node it is. The audit trail record should contain th...

Currently, when archives are shifting, any attempts to create PI Points will be rejected with the error "Error on internal point editing call during point create for archive add point(<point info>). [-11095] Archive Shift already in progress...

Allow a different naming pattern for the child event frames. End result would have the long, uniquely named EFs in the Parent EF as usual, but the Child EFs could have a simplified name, like the level of an alarm that is pulled from an attribute ...