Essentially, the export tags engineering process is “place export tags in subordinate station”, that is, you work from the “JACE side”. Using Workbench, do this by copying export tags from the Extensions folder in the exportTags palette. This is commonly called “tagging up the JACE”.

When you issue the Join command, resulting objects are created in the Supervisor (Figure 8).

Exported components are created in the Supervisor under the NiagaraStation component representing the subordinate station that was joined. This includes Px views (complete with Niagara “virtual points” and imported image files), history and file import descriptors, schedule import and export descriptors, plus components such as Niagara proxy points.

As part of the “JoinProfile” on a subordinate station, a “profile.bog file” on the JACE determines the property values used in the corresponding NiagaraStation (including its device components) in the Supervisor station. Optionally, this profile.bog file can also determine the container/folder structure used in this NiagaraStation in the Supervisor. Each export tag can reference a specific location in this profile.bog station, to be used as the parent container for its associated exported component.

Exported files and histories result in objects created in the Supervisor’s file space (Files) and history space (History), in addition to their associated file and history import descriptors (components) created under a NiagaraStation. Under the Files and History object spaces, created files and histories are automatically organized by subordinate station (not shown in Figure 8).

The following sections explain more export tag concepts: