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.

Add a new idea Subscribe
Status Reviewing
Portfolio area Enterprise SCADA Server
Products Administration / Installation Architecture
Created by Jake Hawkes
Created on Nov 2, 2023

RELATED IDEAS

Support OS live upgradability

Big Picture

Support live OS upgradability after Enterprise SCADA has been upgraded to v2023, without the need for a cold start.

Detailed Description

It is currently assumed that it will be required to update the OS from one major version to the next, without the need to re-install, test, or re-certify the Enterprise SCADA product installed on the server.

Zero down time for the entire system. Meaning that with a distributed system that contains at least primary and secondary site the system can be updated without loosing control of the pipeline. However it should be noted that some customers would not be comfortable running without a backup site, at least not for a prolonged period.

The new OS version must be installable in the same Active Directory (AD) where older versions of product and OS are present.

What follows is a snapshot of the current R&D supported upgrade path. Note that the Global Practice and Calgary Delivery groups are developing a process to support skipping major versions for an upgrade, provided that the older version as at least Enterprise SCADA 2021.




Assumptions

  • some reduction in redundancy is acceptable

  • Customers will upgrade in-place to obtain OS live-upgradability. Those who wish to start with a fresh VM will need to use existing processes to swap them in

    • Some customers are able to leverage things like MQTT and Hypervisor spare capacity to spin up new upgraded systems and test them in parallel, and then put into production by fiddling with the broker

  • 3rd party software is likely on the server

    • cybersecurity at a mimumum

    • servers, interfaces etc from other vendors

  • The abstraction between the product and the OS is defined well enough that only the most dramatic changes to the OS would require product changes

  • The LTSC lifecycle for Windows Server is 10 years

  • The LTSC lifecycle for Windows Desktop appears to be changing from 10 to 5 years, unless we start using the IoT edition...


Risks/Mitigations

  • Changes to Active Directory Functional Level introduces scope increase, and while we are in the dark about details, lots of risk

  • Same for .Net upgrade


image.png
image.png
Open full size
image.png
Expectation

The ability to upgrade the Server and Desktop operating systems upon which my SCADA system is running, without requiring me to shut-in the pipeline, and preferrably, without triggering my change management process.
Idea business value

If the LTSC cycle shortens, this will become critical.

This is a vital part of the product's overall upgradability, but is admittedly lower priority than upgrading the SCADA software, which we would like to see happen annually.
Idea Type Improvement
Idea priority 4 – Important to my company
Work in
OASYS-547 Support Windows OS live upgradability
Work status
  • Attach files