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 Waiting for information
Portfolio area Enterprise SCADA Server
Created by Jake Hawkes
Created on Aug 9, 2024

Provide translated system alarms that cannot be translated with ResX files

Big Picture User Experience

Operators expect all system alarms that they see to be in their native language.

Not all operators in all customers see system alarms, and some have a strict "no system alarm for operators" policy. However, the majority of customers will show some system alarms to operators.


Detailed Description

Not all system alarms can be translated via the ResX files mechanism due to the way they are created and stored in the windows event log.

We either need to re-design how these system alarms are generated and logged, or we need to provide more languages in the product for this sub-set of system alarms that cannot be translated by the project.

From R&D:
Historically and in Enterprise SCADA 2021 There is a certain category of system alarms that are copies of events which are recorded simultaneously in the Windows Event Log. Only a small percentage of the different types of alarms are generated in this way; most notably arbitration events (e.g. services starting, stopping and failing over) and process/system health monitoring alarms. These alarms are administrative in nature, and are not usually of interest to SCADA operators.
The Windows Event Log does not support internationalization of string resources using ResX files and satellite resource assemblies. Instead, it uses compiled message event DLLs, as described in the Windows Developer documentation: https://docs.microsoft.com/en-us/windows/win32/eventlog/message-files.
The message DLLS must be rebuilt, deployed and configured (or “registered”) with the Windows operating system whenever new messages are added, or to add support for new languages. Consequently this is not a procedure that can be performed easily by projects or customers. If additional languages are required, an enhancement request with the translations in required language can be provided to R&D and they will be added to a future release or service pack.


Business Value

To support growth outside English speaking countries, full language support for all operator facing text is required.


Assumptions

These system alarms are simple enough that one translation in the target language is enough. There will not be a need to support variants (like Mexico vs. Spain)


Links

Initial IMS defect request (sonatrack): ADO# 1231322

Product value score
13
  • Attach files
  • Admin
    Jake Hawkes
    Reply
    |
    Aug 9, 2024

    Need to establish the need from our international user base as to their opinions on english-only system alarms. Note also that with system alarm override and handoff, the project can now intercept these alarms and re-write them with custom code.