Cross-Regional peering use cases and boundaries
- Last UpdatedSep 02, 2024
- 2 minute read
|
Cross-Regional Peering Use Case |
Details |
|
UX Latency |
User desktops in a Cloud UE environment are hosted in a specific region, users located long distances from the region can witness compromised user experience due to streaming communications latency. For E3D, Diagrams & Engineering (non COR) project data, this can be mitigated by hosting a second CUE environment in a region closer to these users and synchronising the project data between both Cloud UE environments using AVEVA Global. |
|
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).. |
|
Cross-Regional Peering 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). |
|
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. |
|
No Unified Engineering SAT to Unified Engineering Sub-SATs. |
In this release, only Unified Engineering HUB to one or more Unified Engineering SATs is supported. Unified Engineering SAT to Unified Engineering Sub-SATs are not supported. |
|
All Unified Engineering Environments should be in the same CONNECT account |
In this release, all the Unified Engineering environments in a globalized network must reside in the same CONNECT account. Flex Credits will be consumed from this single CONNECT account. |
|
Unified Engineering SATs must be in different regions to the HUB and other SATs |
In this release, globalization between two Unified Engineering environments in the same region is not supported. |
|
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. |