Big Picture User Experience
Next release of Enterprise SCADA to support of the next MSFT stack of new Operating systems.
Detailed Description
Windows 11 LTSC and Windows Server 2025 are due to be released before Dec 31 2024. We must support these two new Operating systems. The new ES version must support both Windows 10/ Server 2022 and new Win 11/ Server 2025.
Upgradability: Customers shall be able to live upgrade systems both for product and OS at the same time.
Business Value
Staying on a supported operating system is a requirement from Regulators for critical infrastructure systems. To stay current with demand we must keep with MSFT OS systems
As MSFT Operating systems will reach end of life our products must keep up with the operating support and their life cycles.
Target Version
Target version for this feature: TBD
Version the customer is on or consuming: N/A
Version being targeted by project or future opportunity: .
Customer, Project, and Deadline Details
Customers (names/projects) that will consume this: All customer that will be upgrading or new customers onboarding in the next 2-3 years.
Deadlines and Commitments: .
Commercial and/or Contractual Impacts: .
Is this a customer funding candidate?: .
Customers System / Architecture
Size: Small, Med, Large - All
Topology: Single site, Multi Site, and Enterprise - All
Any Unique configuration to note?: Single Historian
Has this functionality been delivered before?: (project / custom code):
If yes, please include requirements, test cases, test data, use-cases, SWANA captures, ADE screens, database .l files
Out of Scope
None Identified
Assumptions
None Identified
Dependencies
None identfied
Upgradability
TBD. We will be asking for live upgrade the OS with the product.
PSR - Performance, Scalability, Resilience
Important PSR aspects for this feature? .
What if there are 10,000 of these? .
How quickly is this expected to react/respond? .
Does this impact failover / mode switch? .
Is this assumed to have performance impact, or not? .
NFR - Non-Functional Requirements
Release Vehicle: released as part of the larger product? Part of ES release.
Compatibility: any explicit compatibility requirements? None identified
Documentation: as usual. This must be documented.
Operating System: N/A
Other AVEVA products: All Midstream products will be effected and must be certfied. This including LMS, HMI, Meas, GDA Data Connector.
3rd Party products: .
CPU / Memory / Disk requirements/constraints: None identified.
Risks/Mitigations
Perhaps. This should be left to the Arch team to evaluate. Spike is required.
Mock-up / Supporting Information
NA
Architecture Review Required?
Yes.
Do we need a SPIKE?
Yes
Links
Aha: .
Jira: .
Class 5 Estimate: .
Implementation: .
