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 Subscribe
Status Waiting for information
Portfolio area Enterprise SCADA Server
Products Alarms Realtime Schema
Created by Guest
Created on Feb 4, 2022

RELATED IDEAS

Ability to add new fields to almsum/event tables in ES2021

One of our water projects will be upgrading to 2021 (or 2022) from 7.5. They've previously customized their almsum and event tables to include an additional field (a record name from a custom table). I know that we can add fields to Realtime tables (and presumably to Historical tables as well) in OASyS2021 but if we added a field to almsum (or event) then there would be no way to modify the baseline alarm/event functions to include a new value for that column.....correct?

Have there been any changes to the Alarming and Eventing APIs that would allow us to add in an extra column to those tables and have the column populate on baseline alarms/events? I've searched through the documentation but didn't see any and thought I would just check to make sure I'm not missing anything.

  • Attach files
  • Admin
    Jake Hawkes
    Reply
    |     Oct 3, 2023

    We should get to the 'why' of this request. What does the second point name signify? What is the problem they are solving with this solution?

    Something that is gaining some momentum is operator annotations - some way for operators to mark the alarm with a category or designation, selected from a pick-list, that would be stored with the alarm. This would be used to analyse the alarm-events, filter and report on the operator annotations.

    Examples are:

    • MAOP related

    • Safety related

    • Nuisance or false alarm

    • etc.

    We have considered beefing up the CRM Note capability, so that through minimal clicks, the operator can create a note and associate it with the event while in the act of acknowledging the alarm.

  • Admin
    Jake Hawkes
    Reply
    |     Feb 4, 2022

    At this time, you can add the fields to the table, but populating them is not supported by the baseline APIs for alarms.

    Also, the APIs for alarms and events are not extensible at this time.