jamesbrandt

My feedback

  1. 37 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    jamesbrandt supported this idea  · 
  2. 3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
    jamesbrandt supported this idea  · 
  3. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    jamesbrandt commented  · 

    I know newer versions of the AF have a regression function.
    However, compression functionality (with the opposite function) would help us with our volatile end calcs used for turbine/generator efficiencies. They can be hard on the eye to use in visualisation tools. TagAvg etc use out of date data impacting credibility of the data.

    jamesbrandt supported this idea  · 
    jamesbrandt shared this idea  · 
  4. 8 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    jamesbrandt supported this idea  · 
    jamesbrandt commented  · 

    The user might also want a tag median based on the last nos. of events, not just timebound.

  5. 3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  OSIsoft Cloud Services » Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    jamesbrandt commented  · 

    A very common requirement, unfortunately currently made difficult in PI. The current workaround requires cascading a busy analogue into hourly buckets and then to daily buckets etc. This is done to take the load off the AF where the only other alternative is for PI to rerun calcs on busy analogues constantly and frequently.

    This approach is difficult as triggers require the pre-requisite values (e.g. hourly) to be calculated before rolling up into the next calculation (e.g. daily). It is possible to hard code the timestamps in the analysis expression to get the required results, although for functions like tagtot, for periodic scheduling it resets values to 0 at midnight even if you require to Output Timestamp to relative trigger time. This cuts-off the calcs for the previous day. The requirement must ensure the values align at similar time intervals, not as a cascading rolled-up sequence that becomes out of sync with real-time).

    jamesbrandt supported this idea  · 
  6. 182 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    37 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    jamesbrandt supported this idea  · 
  7. 89 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    jamesbrandt supported this idea  · 
  8. 104 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    jamesbrandt 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
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED