PI Server
Welcome to the PI Server feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI Server. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.
Please note that your ideas and comments posted here are visible to all other users.
- For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal (https://my.osisoft.com) instead of sharing them on this site.
- For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
-
Option to write Default Value to PI tags created through AF Templates
When creating PI points through AF Templates, there should be an option to "Write Default Value after Point Creation", or some other way to initialize the value of an automatically created PI tag.
Right now, there is no way to replace the Pt Created value with a default value upon creation, and the "Default Value" in the AF Template serves no real purpose for PI Point Data References.
6 votes -
Support "category" for the name substitution parameter in AF template
Use category of an attribute for the name substitution parameter of the PI point data reference
6 votes -
Add the option of using substitution parameters in the Attribute Description field
substitution parameters
6 votes -
Improve management of templates which create PI tags
Currently managing attribute templates which can create tags is very laborious. It is an issue particularly when dealing with different security settings for tags. Improvements suggested would include
- have the ability to create and maintain multiple 'profiles' or templates for tag creation - which for example might be used where different tag security settings are needed
- enable the ability edit an attribute template's PI Point creation settings in PI Builder
6 votes -
AF Templates should show creation and modification dates and creators and changers
AF Templates should show creation and modification dates and creators and changers. Currently AF Elements show creators and modifiers, but AF Templates do not show this information in PI System Explorer. This would make it more obvious when changes happened, without having to dig through the audit logs.
5 votes -
Include AFDiag /AddIdentity functionality to PSE
Adding an identity to an established large system can cause a flood of change records, leading to performance issues.
The AFDiag /AddIdentity feature will bypass this issue, but it would be more convenient to have this functionality included in PSE.
5 votes -
AF enumeration sets should support values with the same name
The feature introduced in 2018 SP2 to manually synchronize digital state sets with AF enumeration sets has a limitation where state sets with duplicated names aren't imported correctly into AF. This is due to the current design of AF enumeration sets that don't allow duplicated names for enumeration values. It would be nice if AF enumeration sets supported multiple values with the same name as it is supported in digital state sets in the Data Archive.
5 votes -
Effective Access tab in PSE works across domains
Effective Access tab in PI System Explorer supports checking for users in another trusted domain.
5 votes -
Create additional Limit trait attributes
Currently there are 7 standard limits available to be used as limit traits. However there are situations where more than 7 are required. Users would like an option to create additional limit traits rather than having to manually configuring additional intervals in PI Vision multi-state.
5 votes -
Allow object specific Audit Trails to be accessed by object level Administrators
Currently to view the Audit Trails of any object on an AF Server, Server level Administrator privileges are needed.
There should be the ability for a user that does not have server level administrator to view the Audit Trails of a specific object or Database they have Administrator privileges over.
5 votes -
Longer passwords PI AF Table Connector
This is really a bug/security risk; but the support team has requested that a "Customer Voice" be raised.
Support passwords longer than 15 characters in the PI AF Table Connector.
5 votes -
Option to reconcile templates during xml import
Suppose the following scenario: a user has 2 AF databases (a development and a production one), both containing same version of a template. The user deletes a few attributes and analyses from one element template (development), exports the xml and imports the same xml file into the production database. Today, the template in the production server remains unchanged, forcing the user to manually delete the attributes and analyses from production database (using either PI Builder or PSE).
The "import xml" function present in PI System Explorer should contain an option to allow users to reconcile templates, when importing a template…
5 votesHi,
So what would be the expected behavior if elements have already been created from the template? It would then be possible to have deletion of data upon an import of a template. What if there are overridden template attributes? What would be the expected behavior if the imported template affects these overridden template attributes? -
Add TimeRangeMethod to StringBuilder DataReference or automatically use StartTime when used on Event Frames.
A frequent PI Square problem regards using StringBuilder DR on event frames and the user wants to see the referenced element's attribute at the StartTime of the event frame. Something like a TimeRangeMethod or UseStartTime flag would be helpful. Perhaps even detect the DR is used on an event frame and default UseStartTime to True.
5 votes -
Substitution parameter from root
As an AF administrator, I want to configure templates with Point Creation using Substitution Parameters that can retrieve names and values from an element relative to the root element and working it's way down to the element wanted. A way for this to work, would be for the search mechanism to store the full path of the element and then work it's way down starting at the root.
Currently substitution parameters can be used to retrieve information from elements relative to the element in which the substitution parameter is configured.
Use case: I would use this template for elements that…
5 votes -
Ignore errors during server library import
As a PI AF administrator or power user, I would like to be allowed to continue loading content from a server library into a database, even if a UOM conflict is detected.
Upon finding a UOM conflict, the library import feature does not allow me to ignore the error and continue loading the content (screenshot1.png), in contrast with the file import feature (screenshot2.png).
Tech Support case #00957957 concluded that this was not a bug.
4 votes -
Sort values numerically/by size when using Time Series Data in PI System Explorer for a numeric attribute value type
Currently when viewing Time Series Data for a numeric attribute value type (e.g Double, Single) in PI System Explorer, sorting the value column will sort the results alphabetically (e.g. 1, 10, 2, 20, 3...) and not by size (e.g. 1, 2, 3, 10, 20). PI System Explorer should be able to sort Time Series Data for a numeric attribute by the size of the value in addition to or instead of the alphabetical order of the values as strings.
4 votes -
UOM field should accept substitution parameters
It would be nice if the UOM field of an AF Attribute would accept substitution parameters. This way if an attribute is a reference to another, the UOMs could also be linked. If the UOM is updated on the source, it would also get updated in the reference.
4 votes -
Substitution parameter for base template
It would be nice to have a substitution parameter to fetch the name of a base template. There is a substitution parameter to retrieve the name of a template: %Template%, but none to retrieve a parent/base template.
4 votes -
Allow bools to be unpacked from Integers
AF should allow you to have a PI Point Data Reference as individual bits within an INT. Ex. PIPOINTA is an int16 or int32. PIPOINTA.0 and PIPOINTA.1...etc.. should be able to be mapped to a bool attribute. (where .0 is the 0th spot in the integer tag).
Reasoning:
When using a PI Connector we have INT tags but also use the individual bits within the INT's as unique bool variables to help conserve traffic. When I use them in AF I need to unpack them. A support person at OSI showed me how to use formula attributes using modular logic…
4 votes -
Display string arrays in the PI System Explorer value field
When looking at element attributes or event frame attributes in PI System Explorer I would like to see [string1, string2, string 3] for the value field of an array attribute, instead of "String Array" as we see today.
When you quickly check out the current values of an EF or element, it much easier to recognize the values you're looking for if you see (a preview of) it directly in the Values field for the attribute.
"Hiding" it under the "String Array" key word makes it more difficult to spot!
4 votes
- Don't see your idea?