Tag management

In both Hybrid Cloud and Cross-Regional Peering communication architectures:

If you are manually managing and creating tags using your own tag register, then this section can be ignored.

Where AVEVA Tag Management Repository (TMR) is required\used on globalized projects, tag management and creation should only be performed at the HUB globalized location for all these projects.

The HUB location is also where the TMR Service and associated SQL Databases reside and where the TMR ENGI database for each globalized project is primary.

This ensures consistent single-location tag management and tag uniqueness for each globalized project.

New tags are propagated via global for consumption at SAT locations.

With TMR ENGI databases for each globalized project set as primary at the HUB location, if an attempt to create a tag from a SAT location is made, users are prompted with a “TMR request error: Tag names not available” message acting as a reminder that tags are created from the HUB location.

The HUB location should be specified before deployment of the Unified Engineering Global Services Add-On.

This is specified in the discovery form.