All ideas

Add native support for the OAuth 2.0 Token Exchange (RFC 8693) grant type in Platform Common Services (PCS) for PI when integrated with external identity providers such as Microsoft Entra ID. AIM must support exchanging externally issued access to...

As a PI Administrator, I want to know which tags are being used at which PI Analysis so I can know exactly if there is already another Analysis writing to a tag and avoid duplicated or wrong data.

We currently have Event Frames generating for machine faults, with child event frames then tracking things such as maintenance team response time etc. Leveraging this data in excel reports is proving difficult however due to the Child Event Frame...

As a user of Asset Analytics I would like to manipulate data quality related flags (such as quastionable, substituted, etc) from my analysis so that I can set the flag when there is a problem with input value statuses.

It would be nice if the PI Analysis Service could pick up a change in the Cache Refresh Interval of any AF Table being referenced by input attributes with a table lookup data reference. Currently, a service restart is required.

When creating new analyses with Asset Analytics, our users sometimes forget to modify the scheduling from natural to periodic, which might lead to high trigger ratios and degraded performance. AF should allow administrators to define the default a...

Build a visual PI System connectivity map that shows how interfaces and servers (etc) are connected from so many different places.

Currently, AIM can only use CONNECT or Microsoft Entra ID as the main Identity Provider. Configuring any other IDP requires federation through CONNECT. Allowing other IDPs to work directly with AIM without CONNECT would simplify the OIDC configura...

Offer a free Community Edition of PI. Limit the point count, but let us geeks monitor our IOT hobbies with PI. This will encourage business buy in and increase general knowledge of OSIsoft throughout the geek community.

Currently notifications are not triggered (send) by events that are more than 72 hours in the past. For me it is necessary to get notifications from events in the (endless) past. Ideally I would like to configure for each notification separately t...