Ideas

Showing 201 of 5209

Allow different permission models and "view effective permissions for user" features within tenant

For sharing data to external clients who are not PI/CONNECT users, we cannot use the community sharing and permissions model and instead have to add users to an org's tenant. By default, all users are granted the tenant member and tenant viewer ro...

Adam Bolin 5 days ago in PI to CONNECT / General 0 No status

244 VOTE

Multiple y Axis

Currently ProcessBook and coresight trend only provide one Y axis. We would to have 2 Y axis to plot different parameter for an asset. Example: Flow parameters can be plotted on Y axis on the left and temperature can be plotted on Y axis on the r...

Guest over 3 years ago in AVEVA™ PI Vision™ / Authoring Displays 12 Planned

154 VOTE

Add Custom Graphics / Images to Graphic Library

Have the ability to 'extend' the Graphic Library provided in PI Vision with additional graphic symbols / images / stencils.

Guest over 3 years ago in AVEVA™ PI Vision™ / Authoring Displays 6 No status

2 VOTE

PI to Connect Agent instance Failover

on behalf of customer: We would like to see agent failover added to PI to Connect. The PI System already provides high availability, and extending this capability into PI to Connect would deliver a resilient hybrid infrastructure end-to-end. Histo...

omar alomari 17 days ago in PI to CONNECT / General 0 No status

142 VOTE

Nesting collections

It would be good if collections were essentially full-blown mini-displays, where you could group/ungroup objects and also include a collection inside another collection.

Guest over 3 years ago in AVEVA™ PI Vision™ / Authoring Displays 13 No status

105 VOTE

Trend Stacking

Ability to stack the trend ranges one on top of another within a single trend.

Guest over 3 years ago in AVEVA™ PI Vision™ / Authoring Displays 7 No status

31 VOTE

Report individual tag count per PI Server, not just aggregation

As a customer using PI Data Infrastructure and CONNECT, I would like to see the individual tag count per PI Server, not just the aggregated tag count SO THAT I can understand the source of the aggregated tags across my data infrastructure.