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 Future consideration
Created by Nina NICHOLLS
Created on Jun 2, 2021

Ability to configure cause codes as decomissioned

https://schneiderampla.atlassian.net/browse/CE-2255[System Info]
Ampla 7.3

[Raised by]
Customer Company: Rio Tinto Iron Ore - WA
Customer Contact: Ben.jones@riotinto.com

[Enhancement Request]

The client would like the ability to set the status of CauseCodes to Active (by default) or Disabled (Decommissioned). Over the years, the Rio Tinto IO Perth projects (OCDT, CLBDT) have acquired many Cause Codes, where, due to the need to preserve historical data (Ampla Downtime Records with old cause codes) they are not able to remove these from the project. This extensive list contains 535 cause codes, of which only 165 are relevant to the project.

This lengthy cause code list makes it quite cumbersome when trying to filter records by Cause in PA, so Rio Tinto would like the ability to control what is presented as an 'active list' of cause codes by eliminating the 'decommissioned' codes through a mechanism such as a configurable property per cause code. I have tried stopping cause codes to see if that prevents Ampla from loading them in PA while allowing old records to maintain them - but this is not the case.

Rio Tinto’s request verbatim, below, with an impact statement.

"
This is an Enhancement request for decommissioned Cause Codes to not appear in the Client “Filter on Cause” popup.
This would require:
• In Ampla Studio, an extra property on the Cause Codes to State Active or Decommissioned (Active by default)
• The Ampla Client does not show these decommissioned Cause Codes in the “Filter on Cause” popup

Some background, in 2015 a project was initiated to use the Effect column and new Cause Codes added. The previous Cause Codes were decommissioned:
• Number Causes Codes in 2015: x365 (these were decommissioned)
• Number Cause Codes added in 2015: x165
• Total: x535

The Gudai Darri project will add more Cause Codes in July 2021.

Impact
In the Ampla Client filter builder, it shows the Cause Codes that were decommissioned in 2015 (Ampla WG project to introduce Effects).
This results in the Filter builder being quite messy and more difficult for an End User to find a Cause Code to Filter on.
The Filter on Cause popup shows x535 Cause Codes, when we only need it to show x165.

"



  • Attach files