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 Nov 21, 2019
Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit AMPLA-I-51 Ability to bulk configure (Relationship Matrix, Heirarchy).

Ability to export Ampla Equipment Heirarchy and Relationship Matrix Merged

https://schneiderampla.atlassian.net/browse/CE-1913

[Raised by]
Customer Company: Rio Tinto Iron Ore
Customer Contact: Ben Jones (ben.jones@riotinto.com)

[Problem Summary]
Rio Tinto would like the ability to export Ampla's Equipment Hierarchy and Relationship Matrix using web services, as outlined below:

"
The RTIO Business (Ampla End Users) require the ability to export the Hierarchy & Relationship Matrix to Excel.
This allowed for a single pane of glass (birds eye view) of the Cause/ Classification / Effect for each Equipment Type in ONE VIEW.
They use these Excel files to understand the Ampla configuration before making “Requests for Change” to:
• Add new Equipment to Hierarchy
• Edit / Add new items to the Relationship Matrix

Current State
• Ampla code object is written referencing internal Ampla DLLs (unsupported by AVEVA) to extract the following to Excel (see attached):
o Equipment Hierarchy
o Relationship Matrix for each Equipment Type

Future State (ie Enhancement request)
• Web Service (CLR stored procedure) access to Ampla Configuration
Could then publish via PowerBI, with export to Excel via PowerBI
• Web Client version of Ampla Studio with read only access to view Ampla Configuration

This is an enhancement to allow NON Ampla Admins to view Ampla Configuration, without the need for Ampla Studio access or Ampla Server admin access.
"