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.

Portfolio area Application Server & OMI
Created by Ernst van Wyk
Created on Jul 28, 2024

Expand Auto-binding capabilities

Auto-binding has the potential to improve productivity significantly by removing the need for complex IO referencing scripts as well as allowing users to test IO assignment in runtime. Auto-binding today can only use the assigned IO device and Scan group with the object name and attribute name, this needs to be more flexible

The idea would be to improve or expand existing aspects of the AUtobinding functionality:


Aspect I: The IO reference syntax

Today the Auto-bind syntax looks like this: <IODevice>.$TemplateName.AttributeName

  • <> to denotes variables used to assemble the IO reference. These can be special reserved keywords or System Platform (AppServer) attribute references.

  • This needs at least four reserved keywords

    • <MyDIObject>

    • <MyScangroup>

    • <IODevice> (this already exists, but since <MyDIObject>.<MyScangroup> will have the same result, we can deprecate it if we want)

    • <Attribute>

    • Consider other building blocks as well:

      • <ObjectName>

      • <HierarchicalName>

      • <AreaName>

      • etc.

  • Provide a mechanism to allow using object attributes directly as well as plain text. This means you can build an Input source as:

    • <MyDIObject>.<MyScangroup>.<me.AnotherAttribute>.<Attribute>.Array[<me.ArrayIndex>].PV

Aspect II: Design-time experience

  • The IO Devices pane usage remains the same

    • User can assign an object to a Scan group on a specific DI Object

    • We should allow a user to designate a default DI Object and Scan group (similar to default area, engine and platform)

  • The Mapping pane should function as it does today, that is: it should attempt to use the assembled IO reference, connect and show live data.

  • Attach files
  • Jim MacDonald
    Reply
    |
    Nov 22, 2024

    I like the idea. How would this relate to the work done by Mike Brost (?) with "Rule based IO formatting"? See attached

1 MERGED

Hierarchical or object use for I/O reference naming

Merged
I would like to see the option of choosing hierarchical or object name reference when using IO source autobuilding. This could be a simple check option in the I/O subwindow. I believe this will limit a fair amount of IO overriding. For example in ...
Dean DeGrazia 6 months ago in Application Server & OMI / IDE 0