Update Tags Registry

An existing Tag Management System (TMS) project can be structurally changed to be compatible with TMR by carrying out a project upgrade.

Such projects have tags that were created using Engineering service, these tags are available in the Engineering database but they wont be reserved in the TMR service. Any tags that don't have a reservation in TMR service can end up having duplicates, for example: 05-FT-01 is a flow transmitter created in TMS, it's counter is 01, because it is not reserved with TMR so TMR logic treats 01 as an available counter for flow transmitters. In such cases another user can create a duplicate flow transmitter with tag number 05-FT-01. To avoid duplicates, all tags whose naming rule either writes to NAME attribute or has a counter should be reserved with TMR service.

The update registry functionality provides the ability to reserve existing tags with TMR service, it scans all existing ENGITE and FUNITE based elements and then updates the TMR service with the tag number and counter information extracted from these elements.

A message window is displayed Update Tags Registry with project data, click Yes to start the update operation. The Update registry window is displayed and a progress bar displays the progress of the update process.

Note:
Scanning and updating the tags registry with project data can take a long time.

Once the update of tag registry has been completed, the Update registry window is populated with the total number of elements scanned, tag numbers processed and the tags numbers not processed (information is also provided for why tag numbers have not been processed). Log files for the tag numbers processed or not processed can be exported.

Consider the following before using the update registry functionality:

• In a Multiple Database (MDB) that has access to all the engineering databases with tags to be updated- the functionality scans and updates all ENGITE and FUNITE based elements in the current MDB (even if they are read-only). Existing tag numbers are expected to be in update with their naming rules.

• Any tags that have a naming rule with a counter are expected to have corresponding counter element(s). Tags that have a naming rule with a counter but not the counter element(s) will not be updated with TMR service.

• Tags created prior to the introduction of counter options will not have counter elements. These tags need to be purged and re-created with Counter override option.

• On a live customer project, if purging and recreating is not an option then the correct counter elements can be created with an ad-hoc script or add-in, contact your local AVEVA Technical Support via the AVEVA Knowledge & Support Center website https://softwaresupport.aveva.com/.

  Note:
  Any tags that have a tag number not conforming to its naming rule has the potential to create garbage data in TMR service. For example - a naming rule is composed of Area Number, Name Precedent and Counter attributes. For such a naming rule a tag number 05-FT-01 should have "05" in Area number attribute, FT in the Name Precedent attribute and 01 as the counter value. If these values are not as expected then wrong data will be updated with TMR service.