Hybrid Cloud use cases and boundaries
- Last UpdatedSep 02, 2024
- 2 minute read
|
Hybrid Cloud Use Case |
Details |
|
For 3rd party products\processes on-prem |
AVEVA is unable to deploy some 3rd-party products in Unified Engineering for legal, compliance and licensing reasons. This use case employs AVEVA Global to synchronize Cloud UE E3D, Diagrams & Engineering (non COR) based project data to On-prem customer infrastructure enabling deliverable production (such as isometrics and reports) using 3rd-party products and processes.This |
|
Workshare |
This use case employs AVEVA Global to enable Unified Engineering project workshare with On-prem for E3D, Diagrams & Engineering (non COR) based project data. This can be simple single-location writeable or multi-location writeable (using extracts). |
|
Hybrid Cloud Boundary |
Details |
|
Globalization of databases for E3D, Diagrams and Engineering (non COR) activities only |
Supporting DESI, PADD, CATA, DICT, PROP, CONF, SCHE, ENGI, RDFN databases. |
|
Same Global-related software versions across all Globalized locations. Global, Admin, E3D, Diagrams & Engineering (where used). |
It is imperative that the versions of software relating to the Globalized databases are the same in all locations (Cloud UE & On-prem) to avoid data corruption. These include Global, Admin, E3D, Diagrams and Engineering (where used).It |
|
Same E3D Series across all Globalized locations |
All globalized locations (Unified Engineering & on-prem) in a globalized network should use the same E3D series (2 or 3) to avoid data corruption. |
|
No Shared Services functionality for Global |
For multi-write workshare with extracts, Shared Manager & Scheduler services are not available in this release of Unified Engineering. |
|
The Unified Engineering environment location should be configured as the Global HUB. |
Configuring the on-prem location as the Global HUB should be avoided as it diminishes AVEVA’s ability to recover all data in the event of a disaster. Under special circumstances, the on-prem location can be configured as the Global HUB subject to AVEVA and the customers agreement to reduced SLA’s. |
|
Tag management and generation from HUB location only. |
If TMR is used on projects, tag management and generation can only be performed at the HUB location for all these projects with tags propagated via global. |