Rick Davin

My feedback

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

    43 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Rick Davin commented  · 

    Another user ( Dave Johnson ) has posted an interesting discussion on this topic at:
     
    PI AF Extensible Analytics 

    Rick Davin supported this idea  · 
    An error occurred while saving the comment
    Rick Davin commented  · 

    In response to Tim Carmichael, "Since I haven't had an opportunity to us..."
    Hi Tim Carmichael
     
    Data References always work on-demand, but an Analysis has the benefit of persisting the output to PI point for history and faster retrieval.  The issue is there are some things that can't be done in Asset Analytics since it lacks a true looping mechanism or conditional branching.  A data reference may access a 3rd party library but configured analytics cannot.
     
    The reason for the proposed idea is to have a standard hooks from Analytics to a calculation service of the customer's choosing (not just MATLAB).  In this use case, Analytics is regulated to be the scheduling service but it shells the actual calculation to an external service.

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

    13 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Rick Davin commented  · 

    In response to James Voll, "Everything you state is EXACTLY what my ..."
    I cannot duplicate your problem.  Today I created a new tag on my data archive.  My examples focus on tag "Sinusoid Previous Value".
     

     
    I quickly created an element with it.  Keep in mind that as it take many seconds or minutes to move from one application to another that the SINUSOID will be changing:
     

     
    Next up is a simple analysis.  We will take the current value of SINUSOID to produce the previous value.  There are a couple of points to note: (1) the expression CurrentValue is not needed in long term.  I only used it to see when I click Evaluate.  And (2), the timestamp for PreviousValue will be TriggerTime.  That is to say the CurrentValue and PreviousValue have the same timestamp.
     

     
    Obviously, PreviousValue is mapped as an output back to my newly created tag "Sinusoid Previous Value".
     
    Next I backfilled for a few days:
     

     
    Using SMT, here's what I show for SINUSOID:
     

     
    And here's what I show for Sinusoid Previous Value:
     

     
    Note there a couple of extra values for the Previous version than for SINUSOID.  Understand that this analysis is triggered whenever the SINUSOID snapshot changes.  However, the SMT archive viewer is showing me values archived values - that is snapshot values that have passed the compression test.  So it makes sense that during the time I was messing with this and performing backfills, that is a little after 11:30-ish AM my time, that the analysis was still running for incoming snapshot data.  But not every SINUSOID snapshot makes it to the archives.
     
    This falls in line with Steve's previous (and nice) explanation, and on my system demonstrates that '*' refers to trigger time and not a wall clock Now.

    An error occurred while saving the comment
    Rick Davin commented  · 

    In response to James Voll, "               "For analytics, '*' does ..."
    What version of Analytics are you using?  You may send a private message to me with the case number(s) so I may review.

    An error occurred while saving the comment
    Rick Davin commented  · 

    Let's back up and correct your original statement.  This is incorrect in regards to Asset Analytics:
     
    '*' refers to now or snapshot values 
    For analytics, '*' does NOT refer to Now but rather refers to the trigger time.  Analytics do not have a notion of wall clock.  Likewise, other PI relative times are relative to that trigger time.  So 't' refers to midnight of the day of that trigger time.  'y' refers to yesterday before this trigger time.
     
    Is this really a critical distinction?  YES, particularly with recalculations, which can be for several days ago.  Each recalculation's '*' refers to its own trigger time (perhaps 2 days ago) instead of Now.
     
    Thus, what you are asking for already exists and is amazingly simple:
     

  3. 51 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 Vision » Security  ·  Flag idea as inappropriate…  ·  Admin →
    Rick Davin supported this idea  · 
  4. 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

    10 comments  ·  PI Server » System Management  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Rick Davin commented  · 

    Pretty sure the requestor means PI SMT's Point Builder.  I am using SMT from the 2018 RC1 and the dialog I see is:
     

    To me the wording is quite clear.  I have the option to remove it from a list or delete the PI Point.

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

    7 comments  ·  PI Server » Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Rick Davin commented  · 

    In response to Stephen Kwan, "Additional details - specifically you ca..."
    When the RC comes out, I will check it out and get back to you.

    An error occurred while saving the comment
    Rick Davin commented  · 

    In response to Stephen Kwan, "Is this to insert a value into an EF att..."
    Yes, it's to capture a value at start time.  However, the value is specifically not coming from a PI point.  Users can already capture a PI point's value at start time.  But they can only capture non-PI points at end time due to the StringBuilder DR.

    Rick Davin shared this idea  · 
  6. 152 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

    28 comments  ·  PI Server » Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
    Rick Davin supported this idea  · 
  7. 21 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

    7 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Rick Davin commented  · 

    In response to Hahnming Lee, "This seems like a recipe for a lot of da..."
    The use-case is having a Rollup Analysis defined on an Element Template, but some element instances may be childless and it messes with other rollups.  E.g. a rollup analysis may be wanting to do a count on an element from among it's child elements, and that first rolled up value feeds into its parent's rollup.  If the first element has no child elements, its count should be 0 instead of throwing errors that are propagated up to the parent element's rollup.

  8. 19 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 » Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
    Rick Davin shared this 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