Approve Tag Changes

Before you begin

Start the collector.

About this task

After you create a collector instance and configure it, you can choose between the following options:

Automatic tag sync: If you enable this option in the configuration file, the collector creates tags automatically in Historian based on the key value. In addition, any tag changes in Habitat (such as adding, renaming, and deleting tags) will reflect automatically in Historian. No manual steps are required.
Manual tag changes: If you disable the automatic tag sync option, any tag changes in Habitat will be captured in the <collector name>_Tag_Unconfirmed.xml file. Only after you approve these changes, they are reflected in Historian.

This topic describes how to approve tag changes manually if you have disabled the automatic tag sync option.

Procedure

Access the <collector name>_Tag_Unconfirmed.xml file. By default, it is located at C:\Program Files\GE Digital\Historian HAB Collector\Server.

Note: This file is named <collector name>_Tag_Unconfirmed.xml only if there are changes for you to approve. Otherwise, it is named <collector name>_Tag.xml, which indicates that there have been no changes since your last approval.
The file contains a list of tags, each tag listed under one of the following sections:
- ProposedTags: Contains a list of tags in Habitat that are supposed to be created in Historian. They will be created after your approval.
- DeletedTags: Contains a list of tags deleted in Habitat, but are not yet deleted/disabled in Historian.
- RenamedTags: Contains a list of tags that have been renamed in Habitat, but still contain the old names in Historian.

For each tag for which you want the changes to reflect in Historian, set the Confirmed parameter to true.

For example, the following code sample indicates that a tag named SUBSTN.LAKEVIEW.VOLTAGE is created in Habitat, but is not yet created in Historian:

<ProposedTags>
    <TAG>
        <TagName value="SUBSTN.LAKEVIEW.VOLTAGE"/>
        <CompositeKey value="SUBSTN.LAKEVIEW.T1"/>
        <MRID value="D3FR67H-F453-4859-SHDKRIBNSJ345"/>
        <SourceAddress value="D3FR67H-F453-4859-SHFURNSOV4853J">
        <CollectionType value="Unsolicited"/>
        <Confirmed value="false">
    </TAG>
</ProposedTags>

To create this tag in Historian, set the Confirmed value to true as follows:

<ProposedTags>
    <TAG>
        <TagName value="SUBSTN.LAKEVIEW.VOLTAGE"/>
        <CompositeKey value="SUBSTN.LAKEVIEW.T1"/>
        <MRID value="D3FR67H-F453-4859-SHDKRIBNSJ345"/>
        <SourceAddress value="D3FR67H-F453-4859-SHFURNSOV4853J">
        <CollectionType value="Unsolicited"/>
        <Confirmed value="true">
    </TAG>
</ProposedTags>

Save and close the file.
Rename the <collector name>_Tag_Unconfirmed.xml file to <collector name>_Tag.xml.
The changes are reflected in Historian:
- Newly added tags that you have approved are created in Historian and data collection in initiated for them. They are removed from the ProposedTags section in the file.
- Renamed tags that you have approved are renamed in Historian. They are removed from the RenamedTags section in the file.
- Deleted tags that you have approved are either deleted or disabled for data collection depending on the value for the TagDeletionType parameter in the configuration file. For more information, refer to Configure the HAB Collector for Tags and Configure the HAB Collector for Alarms. These tags are removed from the DeletedTags section of the <collector name>_Tag.xml file.