Skip to Main Content
AVEVA™ Products Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, select the product of your interest in the left column. Then take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas will first be moderated before they are made visible to other users of this portal.

This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.

Status Will not implement
Created by Nina NICHOLLS
Created on Feb 24, 2022

Additional DT CaptureDataWhen condition : EventStateConfirmOnAutoSplit

Business case:

RTIO uses PI Asset Framework (AF) to auto classify Ampla Records. PI AF takes a few seconds to calculate the Cause, Classification, and Effect. So, an Ampla DT RP with a StartDelay of 30 seconds, would allow PI AF to carry out the necessary calculations_ before _Ampla creates the record (after StartDelay expires). These fields will be configured with the currently available EventStateConfirmOn event, which captures the field values at the time the DT record is confirmed (i.e when the StartDelay expires).

Currently, the DTRPs configured like this are not being AutoSplit, but in the future they will be, with the expansion of the RTIO project. Therefore, RTIO would like AVEVA to consider introducing another event (EventStateConfirmOnAndAutosplit) which would allow these fields to also be autosplit with the values captured at EventStateConfirmOn. This would be similar to EventStateOnAndAutoSplit.

  • Attach files
  • Admin
    Nina NICHOLLS
    Reply
    |
    Oct 10, 2023

    Will not implement as this is a workaround for a very specific scenario and would be a risky change as it would change the core logic of Downtime which is heavily used by customers.