Robert Lyon

My feedback

  1. 20 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

    3 comments  ·  PI Server » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Robert Lyon commented  · 

    Yes, I would like control over the timestamp format in the notification delivery format interface.

    Robert Lyon supported this idea  · 
  2. 57 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  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Robert Lyon commented  · 

    Hi Nate,
    I voted for your idea. I also think that a straight up percentile (by event and by time) calculation would be invaluable. I might put it in as a separate idea.

    Robert Lyon supported this idea  · 
  3. 68 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

    6 comments  ·  PI Server » Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
    Robert Lyon supported this idea  · 
  4. 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  ·  PI Vision » Authoring Displays  ·  Flag idea as inappropriate…  ·  Admin →
    Robert Lyon supported this idea  · 
  5. 181 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

    13 comments  ·  PI Vision » Symbols  ·  Flag idea as inappropriate…  ·  Admin →
    Robert Lyon supported this idea  · 
    An error occurred while saving the comment
    Robert Lyon commented  · 

    My idea would be tooltip configurable with options for most attribute columns (that are available in PSE) including description plus a look-through to PI Point as well if its an indirect reference.
    Also the value of another related attribute where there may be some contextual supporting information.

  6. 154 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

    8 comments  ·  PI Vision » Symbols  ·  Flag idea as inappropriate…  ·  Admin →
    Robert Lyon supported this idea  · 
    An error occurred while saving the comment
    Robert Lyon commented  · 

    We would have many use cases.

  7. 132 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

    8 comments  ·  PI Vision » Manual Data Entry  ·  Flag idea as inappropriate…  ·  Admin →
    Robert Lyon supported this idea  · 
  8. 297 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

    We are aware of the interest in this integration, but at this time we do not have plans to integrate PI Manual Logger with PI Vision. I have updated the status of this item to reflect this.

    Robert Lyon supported this idea  · 
  9. 13 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

    2 comments  ·  PI Server » Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
    Robert Lyon supported this idea  · 
    An error occurred while saving the comment
    Robert Lyon commented  · 

    I would like to add my thoughts. This would provide the same functionality as what I have been thinking I need.
    What I was thinking is that I would like to have an element template with multiple base templates. one use case is similar to Kenneth's, where we would like an equipment template for motors, high voltage or low voltage and variable speed or fixed speed. So at the moment, if we have all four combinations, we need to choose the template hierarchy as either voltage>>speed control type or speed control type>>voltage.
    And then whatever we pick as the lowest in the template hierarchy, we have to maintain the set of attributes in multiple places.

    A similar situation arises where we have a KPI rollup hierarchy. We want the same type of hierarchy over multiple sites. Each site may require different attributes for data input or calculation, so require a derived template applicable to the site.
    We also need to maintain different templates depending their place in the hierarchy. This gets very messy to maintain if you have, say, 3 functional layers, then need to maintain site-specific attributes.

    What I would love is to have, for instance, 4 templates.
    tpt1
    tpt2
    tpt3
    tpt4
    where tpt1 tpt2, tpt3 have no base template.
    But then tpt4 can have base template= tpt1 AND another option called 'include'=tpt2;tpt3.

    Any commonly name attributes could be overriden on the order listed, so tpt3 definition would override tpt2 and tpt1. tpt2 would override tpt1.

    As we move forward trying to standardise solutions across multiple sites, having this flexibility would prove invaluable.

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