PI Server

Welcome to the PI Server feedback page!

We created this forum to hear your ideas, feature suggestions and feedback on PI Server. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.

Please note that your ideas and comments posted here are visible to all other users.

  • For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal  (https://my.osisoft.com) instead of sharing them on this site.
  • For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Automatic Event Frame Name Reevaluation

    I would like to see an option on an event frame generation analysis, probably under advanced event frame settings, that enables automatic event frame name reevaluation at the end time of the generated event frame. Right now I have event frame generation analyses running where I want to use an attribute value as a substitution parameter in the EF name, but the value for that attribute is not retrieved until after the start time of the event frame. Right now I am manually selecting and reevaluating event frame names which isn't sustainable, and I feel that this is a feature…

    3 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

    0 comments  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  2. Event Frame Re-capture/Backfill Option to Save Annotations/Reasons

    When a backfill or "recapture events" option is selected for Event Frames, give the user an option to "Save Annotations" for that specific event frame. Right now, we use Event Frames to copy in Reason Codes and Comments (that are logged as annotations) so we are limited in backfill or recapturing the data if historical data changes.

    6 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  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  3. Outputs at close available for all generation modes

    ‘Outputs at close’ is very powerful and flexible. It allows one to use expression analysis syntax in event frames. Unfortunately, it is only available for generation mode 'explicit trigger', but not for 'pulse', 'step', or 'step continuous'.

    If you want e.g. a new event frame started every time a value of an input tag changes (and closed again when it changes again), generation mode step continuous is what you need.
    In that case it would be very helpful to also be able to use outputs at close.

    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

    0 comments  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  4. RTReport Show Event Frames Between Time Frame

    The ability to see all event frames for a specified range in a time-based report.

    Currently, RtReports doesn't have any capability to list existing Event Frames, whether from specific elements or by any criteria and the only Event Frame reporting capability is for the user to select 1 specific event frame at a time and have that be the context for a run of the report.

    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

    0 comments  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  5. PI Interface for Emerson DeltaV Syncade Batch - Allow EF creation for Phase Step and Phase State level

    Users would like to have the option to create event frames at the Phase Step or Phase State level using the PI Interface for Emerson DeltaV Syncade Batch.

    From the Live Library documentation for PI Interface for Emerson DeltaV Syncade Batch (Emerson start and stop events - Syncade: https://livelibrary.osisoft.com/LiveLibrary/content/en/int-batch-exe-v1/GUID-BE1AAAD0-DF13-4851-A762-2D27845BA73B): "Syncade does not provide phase state or phase step data."

    1 vote

    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

    0 comments  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  6. Event Frames that can expire/auto-delete/archive

    When generating Event Frames it would be useful to automatically remove the Event Frame, either when no longer active or in combination with no longer active and acknowledged, or other conditions.

    An example use case would be for PI Notifications - the need to retain the Event Frames might not be there once a Notification is sent and action taken.

    See https://feedback.osisoft.com/forums/555148-pi-server/suggestions/17219861-ability-to-send-a-notification-without-being-trigg

    For example, I might sent a notification to remind someone to use PI Manual Logger to enter some data, but I don't need an Event Frame to exist after this is dealt with.

    Other examples are that I…

    11 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

    0 comments  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  7. End first child event frame when StartTrigger condition no longer is fulfilled

    Currently child event frames are only created when the following applies:
    + There's an End Trigger
    + There's a second Start Trigger that takes over

    Unlike later child event frames, the first one will not end simply because its own Start Trigger condition is no longer fulfilled. This creates an inconsistency in how gaps between child event frames are handled.

    E.g. PI tag BA:PHASE.1 (cycles through Phase1 - Phase7)

    StartTrigger1: BA:PHASE.1="Phase1"
    StartTrigger2: BA:PHASE.1="Phase3"
    StartTrigger3: BA:PHASE.1="Phase5"
    EndTrigger: BA:PHASE.1="Phase7"
    results in the following event frame periods:

    Child EF1 from the start of Phase1 to the start of Phase3 (No gap!!)
    Child EF2…

    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

    1 comment  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add the option to delete all event frames that reference an element when the element is deleted

    When deleting an element using PI System Explorer, there should be an option to delete all event frames that reference the element. Currently when deleting an element, the delete option "Delete this object and all references to it" does not delete the event frames that reference the element. This delete option only deletes the references that are inside the event frames.

    If a deletion of an element occurs, then there could be lots of undesired event frames that have no referenced element in the database. And to find these event frames, it would be necessary to use another tool such…

    8 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

    0 comments  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  9. Analysis service should include functionality for limiting an Event Frame to x time after the start trigger.

    Timely notification of shutdowns is critical for managing remote unmanned equipment. Control modules outputs may only indicate a fault condition and require and operator to reset locally. Detailed information on the fault condition can be obtained from the control module, but may be delayed fault output by a time period due to controller task priority. Functionality for limiting an event frame to x time after the start trigger is required to provide timely notification of fault codes without waiting for the operator to reset the control module and clear the fault.

    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

    0 comments  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  10. Keeping old events that have been manually worked on in case of Recalculation/Backfill

    Case 1.
    There are some EFs that should be acknowledged and commented by equipment owners. In Pharma World, these comments qualify as GxP and shall not be deleted. Whereas Event Frames generated by analysis can sometimes due to data coming late or analysis errors be faulty. If by recalculation the EF attributes are corrected with data, the user will not be notified of the change, and the comment would be faulty. And if the error is in the trigger tags, and they will be changed afterwards, while recalculating the event would be completely different, and the comments are therefor not…

    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

    1 comment  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  11. Limit visibility of EF to those of which the user has read access to the primary element

    Currently the visibility of Event Frames in PI Vision and elsewhere is only limited by the security of those Event Frames. As the security of Event Frames created by Analyses is dependent on the security settings of the Event Frame template (and those are fixed in Analysis templates) it is difficult/impossible to use templates across an AF hierarchy with different security settings.

    If the user at least could only see those Event Frames where they have read access to the primary element, it would make everything a lot easier.

    Right now, in PI Vision for example, the user can simply…

    1 vote

    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

    0 comments  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  12. Select the EF Template in EF Generation Analyses created from AF Element Templates

    Any AF Analysis that creates Event Frames needs to have an Event Frame template assigned to it, which is used to create the Event Frame. The Security settings of the Event Frame template are used to assign the Security settings of all Event Frames created using this template.

    We are running into the problem, that we have various Element templates being used in the AF hierarchy with differing access rights to those Elements. However, all the EF created in those AF Elements have the same access rights across the complete AF hierarchy.

    One solution is to therefore use different EF…

    1 vote

    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

    0 comments  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  13. Output Acknowledging Event Frame to PI Tags

    AF/EF is used to contextualize the OEE Event. However, because reason codes entries does not include the name of the person who entered the code and/or the time it was entered, we leverage ODBC to gain access to the Event Frame record.

    Due to the reason above, we are storing Event Frame Acknowledgement information to PI Tags. We would like to have some functionality where acknowledging an Event Frame or adding a comment can trigger an Analysis or Notification so that we can output those information to PI Data Archive and eventually save those information (Name, DateTime of acknowledgement) to…

    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

    1 comment  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  14. Purge EFs using AFDIAG and more search criterias'

    You should be able to urge EFs using more complex search criterias' than the ones provide in the latest PI Server 2018 SP3 (StartTime, EndTIme, EF Template).
    Most important criteria would be EF categories, but also some honorable mentions:
    1. EF category
    2. Analysis Name
    3. Primary Element Name
    4. Duration
    5. Others

    7 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  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  15. "Outputs at Start"group

    It would be nice if there were an "Output at start" option to output values at the start of an event frame. Currently there is an "Outputs at close" option for Event Frames.

    63 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

    18 comments  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  16. To have a ‘second’ Reason column available

    It would be great to use Event Frames to classify and afterwards be able to do Equipment Downtime root cause analysis. We’re using Reason codes on the predefined field, however it would be great to have a second available Code Editors than “Reason Code Editor”, like “#machine Code Editor”, giving the chance to insert or select what was the main Equipment causing the stoppage. This means having the possibility of more than 1 dropdown list of selections available.

    3 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  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  17. Store event frame start and end time as DateTime to allow sub-millisecond duration event frames

    Because event frame start and end time are stored as a bigint datatype in PIFD.dbo.AFEventFrame, the precision only seems to be to the nearest millisecond. This is a problem for sub-millisecond event frames. Why aren't event frame start and end times stored as DateTime datatypes?

    3 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  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add an Annotations column to the Event Frames search window

    It would be nice to add an Annotations column to the search page of Event Frames, so that I can better analyze them directly from PSE for administration purposes

    3 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

    0 comments  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  19. late notification

    At times I have event frames that generate late for various reasons that trigger a notification. Since it was late we have no need to get the notification. I would like a way to not have a notification trigger if it is late.

    24 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  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow selection of output timestamp for values written by the outputs at close feature in Event Frames

    It would be nice to have the option to select either starttime or endtime of the eventframe as the timestamp for the value that will be written a PI tag using the Outputs at close feature in Event Frames. Currently, it will only write the value with a timestamp of the endtime of the event frame.

    Use case:

    I have an event frame and I would like to see the average of an attribute value for that duration of that time frame on PI Vision. The expectation is to see a horizontal line indicating the average value throughout the duration…

    22 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  ·  Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your 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