PI Vision

Welcome to the PI Vision (formerly PI Coresight) feedback page!

We created this forum to hear your ideas, feature suggestions and feedback on PI Vision. 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.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Ability to allow Vision users to set and save their time zone

    We are a large company that is across the US. We need to allow users to set and save their time zone within PI Vision.

    7 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →

    If you have a chance, we’d like to learn more about the use case behind this request.

    By default, PI Vision will automatically pick up and use the time zone of the client machine a user is running their browser on, so all times should be displayed in a user’s local time zone.

    If this isn’t the behavior you are seeing, or if you have a use case where users need more control over the time zone being used to display data please let us know.

  2. calculated COUNT of an attribute

    Count of values in tables:

    In tables there are some calculation (MIN, MAX; AVERAGE, RANGE, STDEV,...) available, but no COUNT - I´m really missing it for online reporting, for example: number of cycles or produced pieces based on suitable attributes/tags

    5 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Analytics / Calculations  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support Cross Domain authentication for PI Processbook to PI Vision 2019 Migration Utility

    On an architecture with Utility on a computer located on a different domain of the PI Vision server, the authentication fail.

    Could it be possible to prompt a login window (as for AF)

    4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  ProcessBook Migration  ·  Flag idea as inappropriate…  ·  Admin →

    Currently the migration utility will attempt to access PI Vision as the user who is currently logged into the machine. Could you please share more information about your use case and how would a login prompt be useful in this case? Does the user need to enter login credentials so that they can authenticate as a different user (a user other than the user currently logged into the machine)?

  4. Match Trace Colors Between the Display and Ad Hoc

    In the PI Vision ad hoc workspace, the colors of the traces in the ad hoc trends should match the colors that they were in the display they came from, instead of being randomly assigned a new color when they are added.

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ad Hoc Analysis  ·  Flag idea as inappropriate…  ·  Admin →

    In PI Vision 2019, if a trend symbol is added to an empty ad hoc workspace, the trace colors used in the workspace will be the same colors that were defined in the trend. If there are already data items in the workspace, the colors will be assigned in a specific order so that there are no duplicates.

    When data from any other symbol is added to the workspace, the data items will always get assigned a color in a specific order.

    Please let us know if this is the behavior you are looking for or if you are looking for colors to be preserved in other cases.

  • Don't see your idea?

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED