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
Products Configuration
Created by Ibrahim Elsayed
Created on Mar 17, 2026

Enhancement Request – Deployment Flexibility (Retain Last Deployment State)

We would like to submit an enhancement request that is highly critical during the engineering phase of projects utilizing AVEVA System Platform 2023 R2 SP1.

Requested Enhancement

We propose introducing an additional deployment option across all deployment levels:

“Deploy to / As per Last Deployment Status”

This feature would enable the system to redeploy objects based on their previous deployment state (i.e., only redeploy objects that were previously deployed, while leaving undeployed objects unchanged).

Current Operational Challenge

In a typical project scenario, we manage:

  • ~200 Areas

  • Over 800 Objects

Within this structure, deployment status is often mixed—some objects are deployed, while others remain intentionally undeployed based on engineering requirements.

During routine engineering activities, particularly when performing adjustments at the AppEngine or Platform level (e.g., failover configuration, watchdog timing optimization), it becomes necessary to:

  1. Undeploy the AppEngine or Platform

  2. Apply required configuration changes

  3. Redeploy the system

Limitation in Current Workflow

At present, the redeployment process forces engineers to choose between:

  • Deploying objects individually (time-intensive and error-prone), or

  • Deploying the entire hierarchy under the engine/platform

The latter approach introduces several issues:

  • Unfinished or unvalidated objects are unintentionally deployed

  • Premature creation of object references, communication links, and Historian tags

  • Increased risk of configuration inconsistencies

  • Additional effort required to manually undeploy non-finalized objects

Impact

This limitation leads to:

  • Significant engineering time loss

  • Increased risk of human error

  • Inefficient deployment cycles, especially in large-scale systems

Proposed Value

Implementing a “Deploy as per Last Deployment Status” option would:

  • Preserve deployment integrity during iterative engineering

  • Prevent unintended deployment of incomplete objects

  • Streamline engineering workflows

  • Reduce commissioning time and effort

  • Enhance overall system reliability and maintainability

Conclusion

This enhancement would provide substantial value for large and complex projects, where deployment control and engineering efficiency are critical. We strongly recommend considering this feature in future releases of AVEVA System Platform.

  • ADMIN RESPONSE
    Apr 10, 2026

    Your idea has been reviewed and may have been edited to remove any perceived sensitive information. It is now publicly visible for others to see and vote on. If you are uncomfortable with this, please contact us to reduce the visibility level.

  • Attach files