Technical meetings
- Last UpdatedNov 19, 2024
- 1 minute read
Technical meetings will follow involving stakeholders responsible for deployment tasks up to and including the point of test\handover. This will ensure stakeholders fully understand the technical details and their responsibilities during these phases.
The first step in this phase is to confirm (for the products relating to Globalized databases) that the on-prem AVEVA Unified Engineering product versions align with the versions used in Unified Engineering. This is a mandatory pre-requisite to Global Services Add-On deployment.
The table below identifies the relevant software versions deployed in Unified Engineering 3.3.1.0:
|
Software |
Version |
|---|---|
|
AVEVA Global Server |
3.10.2.0 |
|
AVEVA Administration |
2.1.2.0 |
|
AVEVA E3D Design |
2.1.0.35 3.1.8.1 |
|
AVEVA Diagrams |
14.1.5.0 |
|
AVEVA Engineering |
15.7.3.1 |
If the on-prem versions do not match, then the customer will have to organize upgrading versions, or possibly setting up a separate environment with the correct versions.
The second step is to confirm (for the products relating to Globalised databases) that the on-prem AVEVA Unified Engineering product versions will continue to align with the versions used in Unified Engineering as the AVEVA Unified Engineering environment is upgraded (Cadence is generally Quarterly). This is a mandatory requirement to on-going Global Services Add-On availability.
The final step is to review and complete the Global Services Hybrid Cloud Add-On Customer Discovery form in Hybrid cloud global services add-on customer discovery form. The details provided in this form are used by AVEVA to configure the Global Services Add-On components in Unified Engineering.