Weekly schedule output processing

Each component type varies only by data value category, meaning its Out slot (generally called output) and its In slot (generally called input). The schedule’s output and input are Status <Type> according to schedule component type. For example, StatusBoolean if a BooleanSchedule, StatusEnum if an EnumSchedule.

Typically, only outputs from schedules link to other components for scheduling control, such as writable points of the same type.

Figure 2. Schedules linked to writable points

The screen capture shows a BooleanSchedule and a NumericSchedule, each linked to two writable points. Weekly schedules support status coloring. You can configure colors in Lexicon and using Facets.

Output

Each component has an Out slot and an Out Source slot. In addition, Next Time and Next Value slots are available. By default, these slots are pinned on the component’s shape on the Wire Sheet, as shown below.

Output recalculation occurs upon any of the following:

Any saved change to its configuration
Any change at its input
Station startup
Any change to the system clock

Upon any output change, all of these slots are updated.

Out slot

A schedule’s output value is determined by the following, in highest-to-lowest priority:

Priority	Description
1	To any non-null value at its In slot (if linked) This value is immediately passed to its output. Otherwise (if null), processing continues.
2	If the schedule is not effective, the output goes to the default output value. If the schedule is effective, the output goes to the (highest priority) active special event (if any).
3	To the active weekly schedule event (if any).
4	To the default output value.

Out Source slot

Out Source provides a string “source description” of the current output, as one of the following:

Input
Special Event: <SpecialEventName>
Week:<day_of_week>
Default Output

Examples: “Week: monday” or “Special Event: Christmas Break”