ChristophRose

My feedback

  1. 7 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 →
    ChristophRose supported this idea  · 
  2. 8 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 →
    ChristophRose supported this idea  · 
  3. 12 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Server » Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
    ChristophRose supported this idea  · 
  4. 13 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    This would be very useful. We are using templated elements for usage in collections in PI Vision displays. For example, we want to show various gauges for the temperature, pressure, etc.

    However, since the UoM is fixed in the template, I can't actually include the attribute that is displayed as the value on the gauge in the template. Instead that attribute has to be copy & pasted.

    This has the additional effect of making it difficult to use subsitution parameters, as they are immediately evaluated and the subsituted value is stored in the attribute ConfigString.

    ChristophRose supported this idea  · 
  5. 16 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Server » Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
    ChristophRose supported this idea  · 
  6. 8 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Vision » Symbols  ·  Flag idea as inappropriate…  ·  Admin →
    ChristophRose supported this idea  · 
  7. 115 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    It would be very helpful if this would be supported in PI System Explorer again. As Ben Bohringer noted, it still works, it is just missing in the GUI of PI System Explorer.

    Using PI Builder, it is possible to manually edit the Delivery Format, and add attributes from other elements:

    Adding <osiann:ANInlineContent ContentID="02bb2a93-34ec-4cfc-9624-c1fe5caf4287" ContentProperty="3000" PersistedContentName="..\SiblingElement|Attribute" AdditionalData="" />
    for example gets the Value at Start Time of the attribute "Attribute" in the sibling element "SiblingElement".
    The "ContentProperty" changes what property of the Attribute is selected (I couldn't find a list of what is what, but they can be gotten by looking at other DeliveryFormats).

    This is "simply" a GUI limitation for setting it up, Once correctly added via PI Builder, the attribute even shows up in the designer.

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

    We’ll send you updates on this idea

    15 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    ChristophRose supported this idea  · 
  9. 20 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  PI Server » Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    ChristophRose commented  · 

    We have a lot of summary calculations for event frames (things like minimum and maximum values of certain attributes). For visualisation in PI Vision it would be very helpful to be able to set the output timestamp to the start time of the event frame, as this way viewing the data during the event frame (using an event frame table and applying the time range) would also show the correct value for that summary value.

    Currently the summary value is not visible, as it is written at the very end of the event frame.

    ChristophRose supported this idea  · 
  10. 10 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 →
    ChristophRose supported this idea  · 
  11. 3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Server » System Management  ·  Flag idea as inappropriate…  ·  Admin →
    ChristophRose supported this idea  · 
  12. 294 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    27 comments  ·  PI Vision » Authoring Displays  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    ChristophRose commented  · 

    Its already possible to align objects: In edit mode select at least two objects and then a drop down in the top center is activated allowing you to align or distribute objects.

    An error occurred while saving the comment
    ChristophRose commented  · 

    I'm absolutely appalled that this is not only not available, but that it is not even being planned to be implemented.
    This is an absolutely basic requirement.
    It is one of the main reasons we are looking at using other ways of displaying information.

    ChristophRose supported this idea  · 
  13. 47 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Hi Matt,

    yes it is somewhat of a convoluted workaround and limited to a certain extent (as you mentioned combining day and month does not work). I mostly posted it because it is a solution that doesn't require setting up separate PI Points and Analyses as triggers.

    I am also surprised that the day and month triggers are actually shown in the System Explorer correctly. So there was apparently some work done to support this already. All that is missing is UI elements within PI System Explorer that enable editting directly (instead of using PI Builder).

    An error occurred while saving the comment
    ChristophRose commented  · 

    This is already possible.

    To do this, first create the Analysis in the System Explorer and set the trigger for daily.
    Then load the Analysis in PI Builder (Excel). You can then edit and publish the analysis from there.
    The Column "TimeRuleConfig" will be set to:
    Day=Sun, Mon, Tue, Wed, Thu, Fri, Sat
    To execute every Monday at 00:00, set the TimeRuleConfig to:
    Day=Mon
    To trigger monthly, set the TimeRuleConfig to:
    Month=Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec
    To trigger yearly, set the TimeRuleConfig to:
    Month=Jan
    Of course you can also set the trigger to something like:
    Month=Jan, Apr, Jul, Oct
    You can add an offset of up to one day by adding a Offset=XXXX (in seconds, separated by a semicolon).
    I haven't (yet?) found a way to trigger on a certain day of a month.

  14. 49 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    ChristophRose supported this idea  · 
  15. 16 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    ChristophRose supported this idea  · 
  16. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    ChristophRose shared this idea  · 
  17. 18 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  PI Server » Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    ChristophRose commented  · 

    This would be very useful. When connecting new data sources, it takes some time to check what useful exception and compression settings would be.

    After we have figured out good values, it would be nice to then easily apply them backwards to all the data stored since the beginning, so that any Analyses run on similarly compressed data.

    ChristophRose supported this idea  · 
  18. 38 votes
    Sign in Sign in with OSIsoft
    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 →
    ChristophRose supported this idea  · 
  19. 5 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    So what is needed is a way to remove a single PI Point from the Buffering Subsystem Cache.

    That way, on the next recalculation, the Analysis Server would treat that PI Point like a newly added PI Point, and first retrieve the current snapshot from the Data Archive.

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

    As the customer responsible for this, I'll expand on that a little:
    If I create an Analysis creating a simple SawTooth from 0 to 10, triggering every minute, and let it run live the Analysis Service will apply the compression settings to the Archive data (storing only the 0 and the 10).
    If I "Recalculate" (deleting all the data), the Analysis Service will only apply the compression settings to the last chunk. This is illustrated in this KB article: https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=Will-PI-Analysis-Recalculation-follow-compression-and-exception
    This is irrespective of if a newer Snapshot value exists or not.

    What I expect to happen is that the Analysis Service gives the same result (as long as the input data is the same) when Recalculating and while having the Analysis run live.

    One Use-Case we have for this is calculating (and storing) the slope of a set value, which slowly, but linearly increases/decreases over many hours. When running live, I can simply use the Rate function and be done. If I ever want to recalculate the Analysis (because the Analysis is new and I want to apply it to the last months or years of data), I have to add a lot of code checking the last stored value with the new value. Otherwise I have hundreds of thousands or millions of values archived instead of a few hundred or few thousand, because compression is not applied.

    We have the Buffer Subsytem running on the Analysis Server. It applies (or does not apply) the compression.

  20. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Vision » Look & Feel / Styling  ·  Flag idea as inappropriate…  ·  Admin →
    ChristophRose supported this idea  · 
← Previous 1 3 4

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