Often, you link a trigger schedule to a point extension, not directly to a parent container point or component. In this case, before linking you could first composite the target container component, selecting to expose the extension’s action up in the parent point. Although optional, this can help reusability and link clarity.

Target actions or topics, unlike target property slots, can accept multiple link sources. In some cases, you may wish to link the Trigger Missed slot of the trigger schedule to the same target.

For example, you could link a TriggerSchedule to the ResetElapsedActiveTime action of a DiscreteTotalizerExt, a point extension for a Boolean point used to accumulate runtime. If the trigger schedule is configured to fire only on the first day of every month (at 12:00 am) that extension could be used to hold the current month’s runtime.

Figure 9.   Trigger schedule example

The above figure shows a simple example of a TriggerSchedule linked to an action slot of a DiscreteTotalizerExt, which was composite in the parent Boolean writable. This schedule is configured to fire once at midnight on the first day of every month. The trigger at the ResetElapsedActiveTime slot zeroes the runtime accumulated from the previous month. You can add individual trigger times to trigger schedule. Trigger times populate all triggered events once added. Use Ctrl + click to select the triggered events.