How can we improve PI Vision?

Related Assets: Handle relative parent and child element attributes when swapping asset context

Be able to handle attributes or parent or children from a swapped asset on a element relative display so that their values resolve correctly. 

User story: As a process engineer, I want to be able to build a well display with data from the well’s child assets or parent assets (the field) and have the application swap the appropriate asset context (the well) when I swap the assets SO THAT I can leverage the hierarchical structure on AF that I have built.

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

We’ll send you updates on this idea

AdminTodd Brown (Product Manager, OSIsoft) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
COMPLETED  ·  Alicia Coppock responded  · 

The PI Vision development team has completed work to allow the configuration of related assets for displays in PI Vision 2017 R2. This includes the ability to swap parent and child assets for child assets with consistent naming. Upgrade to PI Vision 2017 R2 to take advantage of this and other key new features. You can read about what’s new in PI Vision 2017 R2 in the release announcement:


Sign in Sign in with OSIsoft
Signed in as (Sign out)
  • Jon M commented  ·   ·  Flag as inappropriate

    this works for child assets with consistent naming, but not for sibling or parent assets. can we this extended to parent and sibling assets?

  • Philippe Cloutier commented  ·   ·  Flag as inappropriate

    Adding this function to the top drop-down menu would be great. It would make navigation smooth since we wouldn't have to necessarily build a table with the All Descendants function.

  • Philippe Cloutier commented  ·   ·  Flag as inappropriate

    The 2017 release is able to do this :

    - Create a table containing the Parent Elements names, with a Navigation link (check 'Change context of current display' and 'Use current asset as root')

    - Create an asset comparison table with the Child Elements attributes and create a Collection Criteria (input the current Parent Element, in Edit Collection Criteria > Search Root, and check Return All Descendants).

    This should allow you to see all the Child Elements when selecting one Parent Element from the table at 1). Please note this will only work if the display is not in edit mode.

  • AdminJohn Swartzentruber (Engineering Manager, Software Development, OSIsoft) commented  ·   ·  Flag as inappropriate

    The 2017 release will provide features that will partially meet the requirements for this story. I say partial because it requires the use of URL parameters or navigation links (that is, it is not supported using the current asset dropdown selector). It also requires that attributes and child elements be named the same across the hierarchy, although the use of the new Collections feature might provide a workaround for the naming issue.

    We will be looking at this more in future releases, and will be looking for specific user cases at that time to be sure we are meeting the real needs of our customers.

  • Vadim Fedorov commented  ·   ·  Flag as inappropriate

    Related asset feature should be more sophisticated. E.g. when you have several references to the same Fan you should be able to to filter out duplicates in the related assets.

  • Jon M commented  ·   ·  Flag as inappropriate

    yes please add. element relative behavior on children work fine as long as generic names are used, but accessing a parent's attribute loses the element relative behavior. in processbook, i could work around this using the .. notation for going back up the hierarchy.

  • twipf commented  ·   ·  Flag as inappropriate

    It would be beneficial to also have the display show the parent / child element right in the name so you know which parent element you're selecting the child from. I.e Plant A / Vessel 1, Plant B, Vessel 1 currently only shows as Vessel 1, Vessel 1, would like to see the plant included in there.

  • ehoffman commented  ·   ·  Flag as inappropriate

    This is a major pain point for us with many of our displays. Many of the displays we build are universal between our sites and being able to switch on the parent element template would make this much easier and allow more options for displays in coresight. You can do this Process Book but not yet in coresight. Please add this to the enhancement list.

  • Colt Hegardt commented  ·   ·  Flag as inappropriate

    Additional explanation:
    The customer has an AF Hierarchy set up with Substations and Buses. When switching between substations in Coresight 2016 Asset Swap the attributes at the parent substation level switch with asset swap but the child Bus element based displays do not swap.

  • Ales Soudek commented  ·   ·  Flag as inappropriate

    This actually needs to be linked to the AF tree view , like the PI WebParts or ProcessBook element relative displays.

  • AdminTodd Brown (Product Manager, OSIsoft) commented  ·   ·  Flag as inappropriate

    Summary: Enhance the related asset feature of PI Coresight to allow swapping a parent asset in an AF hierarchy

    Customer Issue: The related assets feature of PI Coresight only allows changing the element path to the element that is the direct parent of attributes shown on the display, it does not allow changing the path further up the hierarchy.

    Enhancement request: Enhance the related asset feature of PI Coresight to allow swapping a parent asset in an AF hierarchy.

    If you have a display showing the following:

    \\AFServer\AFDataBase\PlantA\Fan1|Fan Speed
    \\AFServer\AFDataBase\PlantA\Fan2|Fan Speed
    \\AFServer\AFDatabase\PlantA\Fan3|Fan Speed

    Where PlantA is based on the Plant template and the fans are based on the Fan template.

    Enhance PI Coresight to be able to specify \\AFServer\AFDataBase\PlantB in a URL parameter to change all symbols so that they then show:

    \\AFServer\AFDataBase\PlantB\Fan1|Fan Speed
    \\AFServer\AFDataBase\PlantB\Fan2|Fan Speed
    \\AFServer\AFDatabase\PlantB\Fan3|Fan Speed

    Note: This was previously Enhancement 115243.

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