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.

ADD A NEW IDEA

Clear

Ideas

    Showing 19 of 776

    Support time series analysis in thread logic block

    When doing time series analysis, right now there is no possiblity to let the thread look for a previous or next event (like in PI PE syntax). This makes time series analysis more challenging as one has to define a specific time range and look with...
    Hans-Otto Weinhold 6 months ago in Advanced Analytics 0 Needs review

    Better Preview possibilites of Thread reload

    When creating a thread logic, right now there is no backfilling preview feature available which would allow to get a preview on an event creation logic within a logic block or when doing a calculation. It would be good to have a similar preview fe...
    Hans-Otto Weinhold 6 months ago in Advanced Analytics 0 Needs review

    Improve calculation for availability for long running downtime record

    In the customer project, there has been a long running downtime. For the metrics records, during the current shift period, the availability which should be 0 (since there is an active long downtime record) shows a value greater than 0. After the p...
    Nina NICHOLLS about 1 year ago in Production Management (AMPLA MES) / Downtime 0 Future consideration

    Expose AVEVA Advanced Analytics outputs to Data Hub - e.g. recommendations

    the key output from AAA is often not just the anomaly score. More interesting will be things like ideal running conditions, ideal model conditions.
    Guest almost 2 years ago in Advanced Analytics 0 Needs review

    Update Duration for manual downtimes

    In Ampla, duration is automatically updated only for open downtimes captured by Ampla (automatic). Manual open downtime durations are not updated automatically. Usually, a code item has to be written to update the duration of manual downtimes. Ref...
    Priyanka VINAYCHANDER about 6 years ago in Production Management (AMPLA MES) / Downtime 0 Future consideration

    Events duration column should be a timespan rather than a decimal

    When viewing events in AVEVA Advanced Analytics, the duration column shows the event duration as a decimal value representing the number of hours the event was open. For example, a duration of 0.1 = 6 minutes. This is not immediately intuitive, an...
    Guest about 1 year ago in Advanced Analytics 0 Needs review

    Overlapping downtime events

    We have request from both Alrosa and Polyus to allow for some mechanism to identify downtime records which overlap. Currently you can have overlapping records for manual records.
    Mehrnoosh KHODAVERDY over 5 years ago in Production Management (AMPLA MES) / Downtime 0 Future consideration

    Access to Ampla Downtime Configuration via webservices

    [Enhancement Request]Customer would like the ability to extract Downtime RP related configuration information through Ampla Web Services/CLR. Currently, Delay Accountants contact the Ampla Maintenance Group to get this information where the mainte...
    Nina NICHOLLS about 6 years ago in Production Management (AMPLA MES) / Configuration / Downtime / Web API 0 Future consideration

    Provide the ability to add conditional mandatory fields in the downtime delay entry form

    Ideally, a user could be forced to add additional info when they select a specific value in a delay entry form field. e.g. When a user selects 'Broken, damaged, Bent' as a cause code, force them to provide some form of comment. Mechanical failures...
    Chris MASTERS almost 7 years ago in Production Management (AMPLA MES) / Client / Configuration / Downtime 0 Future consideration