“System Tags” support is available in the Niagara History Import Manager. This provides an alternate way to import histories from remote NiagaraStations, using “Niagara system history import descriptors”. This allows you to import many histories at once, instead of individually importing histories “one at a time.”

For this to work, remote history extensions (for histories to be imported) must be configured with “System Tags” property values. Refer to the NiagaraAX User Guide section “Configure history extensions” for related details.

Instead of using the import manager’s “Learn Mode” (Discover) to add history import descriptors, you manually add new descriptors in the Niagara History Import Manager, by selecting NiagaraSystemHistoryImport in the “Type” drop-down control of the New popup dialog, as shown in Figure 105.

In the resulting New dialog for the system history export descriptors, you enter one or more “System Tags” as a text pattern, as shown in Figure 106.

You can enter multiple System Tags in this “System Tag Patterns” property, using a semicolon (;) as delimiter between System Tags. In addition, you can use an asterisk (*) as a “wildcard” when entering System Tag values. In the Figure 106 example, the System Tag Patterns value is:

AHU*;Ltg1;Ltg3;Ltg5

In this example, remote points with history extensions configured with System Tags property values including an entry beginning with “AHU” and/or “Ltg1”, “Ltg2”, or “Ltg3” will be imported after this is added and executed. For example, history extensions with a System Tags property value of “AHU1”, AHU_1”, “AHU 1”, “AHU2”, and so will be included, as well as those including “Ltg1”, “Ltg3” and “Ltg5”, but ones with a System Tags value of only “Ahu1”, “Ltg2”, or “Ltg 1” will not.

Note that other properties like Execution Time, Capacity, Full Policy, and On Demand Poll Enabled apply to the associated imported histories, and operate the same as for regular HistoryImport descriptors. See Niagara History Import properties for further details.