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. Write business data to PI Vision display

    To be able to add business data coming from existing business systems into PI Vision displays.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →

    While we appreciate the interest the community has for this suggestion, we have decided to decline this item in favor of other high priority work the product needs. Thank you for your feedback, and please continue sharing suggestions for how we can improve PI Vision for you!

  2. Table: Event-weighted calculations

    We need the ability choose event-weighted averages in the Table similar to what is offered in DataLink.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →

    While we appreciate the interest the community has for this suggestion, we have decided to decline this item in favor of other high priority work the product needs. Thank you for your feedback, and please continue sharing suggestions for how we can improve PI Vision for you!

  3. LOTOS PJ

    If you align value items to left or right it does not work in longer period of time.
    The items move depending on digit numer displayed (attachement VALUES):
    1. Good to have option set decimal digits,
    2. Good to have option TEXT SIZE,
    3. Do not change VALUE ITEM size dynamicaly - let me do that by options.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →

    While we appreciate the interest for this suggestion, we have decided to decline this item in favor of other high priority work the product needs. Thank you for your feedback, and please continue sharing suggestions for how we can improve PI Vision for you!

  4. table: column with attribute settings

    I would like to have the possibility to add an extra column to tables that contains the settings of an attribute. In my case I want to see the PI-Tag-Names that are used for the attributes of an element.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →

    While we appreciate the interest the community has for this suggestion, we have decided to decline this item in favor of other high priority work the product needs. Thank you for your feedback, and please continue sharing suggestions for how we can improve PI Vision for you!

  5. Future Data Attribute Limits

    We are utilizing future data and would like to utilize a Limit on a formula that uses future data. However my static limit does not extend into the future like I think it should. My goal is to see what future dates my temp might exceed my limit. I don’t want to create a future tag for this value. I would think that since it’s just a attribute value with no pinpoint or formula references that the data would just extend into the future. Can this be added as an enhancement to the next version of PI Vision?

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →

    While we appreciate the interest the community has for this suggestion, we have decided to decline this item in favor of other high priority work the product needs. Thank you for your feedback, and please continue sharing suggestions for how we can improve PI Vision for you!

  6. Table with more than one Timestamp

    For reporting reasons I need a table with more than one timestamp (see my dilettantish manipulated screenshot). The time range should be the time range of the disyplay (of course). The options should be time step (e.g. seconds, minutes, hours, days, months, years,...) and value retrieval method (automatic, at or before time, exact time,...).

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →

    While we appreciate the interest the community has for this suggestion, we have decided to decline this item in favor of other high priority work the product needs. Thank you for your feedback, and please continue sharing suggestions for how we can improve PI Vision for you!

  7. Use of functions like "bom" in PI-Vision timebar

    It would be great if could use functions like "bom" (and similar, e.g. bod, bonm) in the PI-Vision timebar. New functions like "beginning of year", for example, would also be great

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →

    There are ways to achieve this using PI time with different syntax. Please reach out to TechSupport with more information.

    There are no current plans to implement functions like bom, bod, etc.

  8. Identification / labeling of changed (manually edited) values within reports

    For pharmaceutical environment is would be an great option to indicate on displays (e.g. Coresight) whether or not an AF attribute’s value or a PI tag’s archive value has been manually edited. The way of indication dosn't really matter, could be a color, footnote, label, ...

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →

    While we appreciate the interest for this suggestion, we have decided to decline this item in favor of other high priority work the product needs. Thank you for your feedback, and please continue sharing suggestions for how we can improve PI Vision for you!

  9. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →

    While we appreciate the interest the community has for this suggestion, we have decided to decline this item in favor of other high priority work the product needs. Thank you for your feedback, and please continue sharing suggestions for how we can improve PI Vision for you!

  • 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
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED