Add a ScheduleExportTag as the child of an existing Niagara ScheduleImportExt under an existing schedule component, that is, a BooleanSchedule, NumericSchedule, etc. that resides in the Schedules extension of the NiagaraStation component that represents the Supervisor. Note this is the only valid parent for this export
tag type. Ordinarily, such a schedule (with a ScheduleImportExt) is created using the online
feature in the Niagara Schedule Import Manager view of this NiagaraStation. In that way, the imported “slave” schedule is pre-configured,
matching the (typically) already configured “master” schedule, as it resides in the Supervisor.
To use a ScheduleExportTag to “slave” to an existing schedule in the Supervisor, you must know that Schedule’s ord (component path) in the Supervisor station—in which case, use of this tag is actually not needed. Instead, you could just enter that ord in the “Supervisor Id” property of the schedule’s ScheduleImportExt.
Or, you can use a ScheduleExportTag with a new schedule to create (as a result of a Join) a new, blank, “master” schedule on the Supervisor that corresponds to the “slave” schedule on the subordinate (JACE) station. This may be how this export tag is used the most. Using this method, you first manually make a new schedule in the Schedules extension of the NiagaraStation (for the Supervisor) in the JACE station, using the Niagara Schedule Import Manager view. Then, add this ScheduleExportTag to its ScheduleImportExt, and configure it to “override” the Supervisor Id station slot path. Upon a Join, the new schedule on the Supervisor resides under the NiagaraStation component that represents this subordinate (JACE) station.
See To add ScheduleExportTags for a “quick start” procedure on working with these tags. The remainder of this section provides more details on this export
tag type.
The following sections provide more details on HistoryImportTags: