Keith Pierce

My feedback

  1. 228 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  ·  PI Vision » Analytics / Calculations  ·  Flag idea as inappropriate…  ·  Admin →
  2. 25 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

    5 comments  ·  PI Server » Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
    Keith Pierce shared this idea  · 
  3. 33 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

    5 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    Keith Pierce supported this idea  · 
    An error occurred while saving the comment
    Keith Pierce commented  · 

    i want to add a clarification to this. As noted previously, the default is "append" and not "replace". In case there's a difference from archive and future files, this should apply especially to future tag streams. It's very common to get multiple forecasts for the same measurement. For example, if we have a future tag for temperature forecast, we often get updates to this forecast frequently. But the value is often in the calculation (analysis) that uses the weather (or other) forecast for a more important business need, like power demand, or power generation forecast. We often see a 7 day window of 15 minute temperature forecasts that are updated daily (after the model runs). This means any given 15 minute period will get many updates. The analysis that runs to create the power demand or power generation forecast will be run many times. We only really want to persist the most recent one (in most cases). Currently, each analysis result is persisted so that when you trend it, there's a vertical trend representing the variability in the forecasts, not the last one. There does not appear to be a simple way to address this now. Thanks.

  4. 62 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 Vision » AF Integration  ·  Flag idea as inappropriate…  ·  Admin →
    Keith Pierce supported this idea  · 
  5. 146 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 » Authoring Displays  ·  Flag idea as inappropriate…  ·  Admin →
    Keith Pierce supported this idea  · 
  6. 404 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

    Keith Pierce supported this idea  · 
  7. 61 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 Vision » User Experience  ·  Flag idea as inappropriate…  ·  Admin →
    Keith Pierce supported 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