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.
-
multiple instancnes of analysis service
As a PI administrator I would like to be able to create multiple instances of "PI Analysis Service" windows service for these reasons:
- avoid new potentially problematic analysis from affecting the ones that are operational and working correctly by setting one production instance and one test instance for example.
- every instance could have its own log files and we could move some analyses to a new instance to troubleshoot them
- make possible to distribute the resources usage for asset analytics on more than one serverThe idea was already declined in "https://feedback.osisoft.com/forums/555148-pi-server/suggestions/33839161-multiple-instances-for-asset-analytics" nevertheless i think…
20 votes -
Ability to disable load shedding on Individual analyses
As a PI Admin I would like the ability to disable load shedding on individual analyses. This will ensure that critical analyses do not skip without having to disable load shedding at the service level and potentially impact performance.
7 votes -
PI System health and diagnostics monitoring
As a customer with a large foot-print of on-prem PI System software across multiple sites, I need a solution for health monitoring and diagnostics that allows me to identify issues (potential or current) with any component of the PI System or its data flow. PI System is a mission-critical application in my organization and any downtime has serious impact to the operations.
As a PI Administrator, I have been asked to use the PI System Monitoring AF toolkit, which is a service, and not a licensed product by OSIsoft/AVEVA. My organization has invested time and resources on implementing the toolkit…
17 votes -
Further development of PI AF scripting functions
In many UseCases we need more programability functions in PI. As example loop functions. We like the AF Framework, beacuse if you search in case of a problem you are very fast. But the functionaclity is unfortunatly not very rich.
Please integrate some more functions or integrate NodeJS, Phyton or
other scripting capabilities11 votes -
Further development of PI Notification
Unfortunatly PI Notfication is an very old tool.
The Tool is very old and slow.
Improvements are needed.Improvements needed:
1. Performance Update for the engineering tool in the AF is very poor
2. Functionality to send an event to an webapi is very basic. we need more functionality to connect also webapi's with a very strong authentification concept10 votes -
Multi Language Support for AF Elements and Attributes
We use PI in an multilingual context.
Therefore we need an functionality to support.It would be good if you could enter a translation list for several languages for all elements and attributes. This language must be selectable and accessible via all interfaces as well as via PI VIsion.
10 votes -
Improve PI Data Security
The assignment of a PI tag on which the currently logged in user has no authorization as PI point reference to an AF attribute must not (as currently) be possible.
It is possible to bypass the PI Archive authorization mechanism (point and data security) by using such attributes in AF-Analytics.The error messages that appear when saving in the System Explorer should not be allowed to be skipped.
15 votes -
Offer extended support for PI ProcessBook for security updates only past 2022
As other vendors do, offer customers the option to purchase extended support for PI ProcessBook for security updates only past 2022 for at least one year, and reevaluate annually based on number of customers interested.
This would only apply to security-related fixes, not enhancement or other functionality updates.
35 votes -
Standard Connector for Microsoft PowerPlattform
To use the PI Server with the Microsft PowerPlatform, a custom connector is required.
This connector is always under the responsibility of the customer, which makes it difficult to keep up with adjustments to the PI system and Microsoft, or to react to them.
Instead of the custom connector there should be a standard connector, which is supported by OSIsoft and Microsoft.
Through this connector the two platforms can ideally work together.7 votes -
Make failback function optional
In the DA collective there is a function called "Failback". The function is described as:
<< When the collective member which the client application was connected to becomes unavailable, the client connection starts monitoring when the member becomes available again. When it happens, it should switch back to that member.
This is done by the client application (it is not anyhow forced by the server) and it is done to:
Honor connection priorities
Restore connection distribution (if member priorities are equal). >>The problem with this is that if primary has been down for a while the buffer needs to…
6 votes -
Add 'Stopped by user' status for analysis
As an AF administrator, I would like to understand the difference between an analysis that is stopped by an end user, or an analysis that has stopped but should likely be running. Currently when an analysis is stopped, we do not know if this is expected or not.
It would be to offer an additional 'status' like 'Stopped by user' or similar.
5 votes -
Data Collection Manager User management
We are running a central DCM Server in our site to maintain the dataflow between different UA Connectors and different DataArchive/AF pairs. We use this DCM to restart Connectors and to browse and select new Tags on a OPC UA Server.
As central Admins, we need the input from our plants in order to select the proper tags to be transmitted into DataArchive. As DCM tagbrowsing and selection is easy to use, we would like to provide our plant DCS engineers the possiblity to do the selection on their own, without our support. But as we are running DCM as…9 votes -
several Instances for PI Relay
Having the PI Relay for OPC UA Connector running on a different machine than the actual connector is a good Idea, as we are now able to provide Windows credentials for AF Access without Credential manager.
On our Site we are running several smaller PI Server and would like to have one or a few central Relay server instead of a Relay per DataArchive. However, this is not possible yet as Relay Service can not be instanciated and only provide a 1 by 1 connection to a DataArchive/AF Server pair. Our workaround is to install the Relay service locally on…9 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 -
Negative numbers in digitalsets
Negative numbers in digitalsets for all PI interface and skip numbers, basically that the digitalset is like the enum of AF
5 votes -
Add support for multiple SortFields in AF Search
Currently, AF search results can only be sorted by a single field. It would be useful to have the capability to specify 2 (or more) SortField values so that the order of results can be guaranteed in the result of a tie.
For example, being able to sort Event Frame Search Results by both StartTime and EndTime.
22 votes -
Provide a way to add Haystack, Brick or ASHRAE 223 meta data markers/tags to PI points or within AF.
Commonly used fault reporting software, such as SkySpark, visualization, GIS and Advanced Analytics applications are requiring metadata/markers embededded in the tags in addition to Tag Name, Timestamp and Value.
Not having a native way to add these meta data markers to PI Points makes it significantly more difficult to get Building Automation data from PI to non PI applications in order to get the most use out of the data.2 votes -
delete tags automatically created by attribute template if related element is deleted
if one element is deleted, the related tags which is created by attribute template can be deleted automatically
2 votes -
have event frames with multiple start triggers match preview results when the parent start time is adjusted during reconciliation
As a PI System admin, I would like event frames with multiple start triggers to match preview results when the parent Event Frame's start time is adjusted during Event Frame reconciliation. Currently we have to take one of the following actions to prevent the duplicate event frames:
Wait until the event frames are closed and then recalculate the event frame analysis
Manually delete the duplicates
Reconfigure our Event Frames to contain just one start trigger
4 votes -
Add relevant windows service dependency via installer.
Following KB01345 & 000036461 we have to manually add dependency where applicable.
Please consider adding similar service dependency than we have via PI ICU for new interface (depend on pibufss):
- AFService depend on relevant MSSQL$<SQLInstance> service if SQL Server = AF Application server
- AF Analytics, AF Notification & PI DAS RTQP depend on AFService if on same host
- PI Web API Crawler on PI Web API
- PI Web API on AFService if target AF is on same host
- PI Web API on Buffer subsystem if already configured at the moment of install/upgrade
- AF Analytics…13 votes
- Don't see your idea?