Store PI Data Archive information in an SQL Server database
Most of the PI Data Archive information that is accessible from PI System Management tools is perfect for a relational database: PI Identities, PI Mappings, PI Point attributes, PI Message Logs, etc.
Moving all of this to an SQL Server database w...
I see too often customers struggling to find the right exception and compression settings. When exception/compression are not well defined, they end up having too many values or missing values, what causes a lot of problems when the affected tag i...
Many of the tuning parameters have units, but the unit can only be found in the tuning parameter's description and is not written consistently (sometimes written in full, sometimes abbreviated, sometimes written as a symbol). Linking the tuning pa...
Being able to activate the Log of abnormally long request made to the PI Data Archive
It would be helpful to determine which users or applications made heavy requests to the Data Archive Server.
This could be an option to be activated or not.
Logging the ip, user identity, concerned tags, duration of the request
Those information a...
jerome.boudon
over 2 years ago
in Data Archive
0
Declined
I have a particular application for storing partial discharge events into the PI Server. Many of the events are at the same timestamp, which result in multiple events at the same time.
Preserve variable-attribute mapping upon attribute path change
Currently, if a variable is mapped to an attribute and the attribute's AF path changes, the variable must be remapped to the attribute.
Instead of relying on the attribute's full path to identify the attribute, each attribute should be identified...
AF function PrevEvent() should return timestamp of previous event even if data is "No Data"
Normally AF function PrevEvent() returns the timestamp of the previous event for a specified timestamp.
But if the previous event is system digital state "No Data" it does not return the timestamp but again system digital state "No Data". That is...
Currently it is only possible to specify one timestamp override per analysis. I would like a way to set a conditional based timestamp override that way the output timestamp could vary based on the result of an analysis.
Introduce jump labels in analysis expressions or attribute config strings
The traceability of cross-element analysis in the PI System Explorer would be greatly improved by using jump labels on relative or absolute paths in the expression or in the ConfigStrings.
For example, you could jump to the referenced element or a...
As control engineer, i think it´s necesary to include some flow control functions, as for next, while, etc; and the capacity to do Iterative functions.