When you click in the Supervisor’s export tag Category Filter Manager, a popup dialog appears asking how many (the only type selectable is Category Filter). Following this, another popup dialog for configuration appears, as shown in Figure 14.
The following fields are in this dialog:
-
Name
Name of each CategoryFilter component, where each must be unique.
-
Station Info Property Filters
This is where you enter the name/value pair that matches a slot in the “Station Info” under the JoinProfile of one or more subordinate stations. Note that in each field, case must be exact.
-
Property — this is the slot name, for example, “State” or “City”.
-
Filter — the string value of that slot to filter on, for example, “Virginia” or “Richmond”.
If needed, use “wildcard” (asterisk) characters, for example “*Carolina*” for slot “State” could potentially filter on “North Carolina” and “South Carolina”.
Use the
plus control to add fields for additional name/value pairs, if needed in the filter match. If using multiple pairs in the
same filter, all must be true (match) to apply the category mask. If needed, click the 
delete control to remove the fields for a name/value pair.
-
-
Category Mask
Click the double-arrow
control for a popup dialog listing available Categories in the Supervisor, as shown in Figure 15.
Category configurations (and names) vary greatly from one job to another. Your Supervisor will have different category names
and likely even more categories.
Click to select and deselect categories. If “Wildcard” is checked, this is similar to “Select All”, plus any new (future) categories will also be selected. Other buttons are self-explanatory.
After adding the category mask, it appears in the New or Edit dialog using hexadecimal notation, reflecting a bitmapped weighting by category indices, e.g. “
14” or “ff”, or “*” if Wildcard is selected.
The button allows you to check the configured “Station Info Property Filters” against the Supervisor’s collection of “Station Info” in all of its NiagaraStation components (since the last Join from each), and provides a “total match count” for each filter selected.
Category filters are applied to components, files, and histories of a subordinate as represented in the Supervisor, when you issue a Join from (or to) that station. Figure 16 shows the Category Browser view in the Supervisor station following a Join from remote subordinate “subJACE_A”.
In the Figure 16 example, “Station Info” in the subordinate’s JoinProfile includes two slots/values: State=Virginia, City=Richmond. A matching CategoryFilter in the Supervisor applies a category mask including categories “General”, “RegionEastMid”, “HVAC_core”, “Ltg_Core”, and “Operations” (some are not visible in the figure).
The order of CategoryFilters can be important, as they are evaluated in order from “top down”, as only one CategoryFilter (and associated category mask) is applied to any NiagaraStation. In other words, category masks are not “multiplexed”
or “additive”. See Figure 13.
In addition to components under each NiagaraStation, categories are also applied to files and histories of stations too. Figure 17 shows the Supervisor’s Category Browser in the Files and Histories sections.
In the initial release of export tags, CategoryFilters do not apply to histories created as a result of a SystemHistoryImportTag, only from HistoryImportTags. You must manually apply categories to histories created with SystemHistoryImportTags, if necessary.