Each component type varies only by data value category, meaning its Out slot (generally called “output”) and its In slot (generally called “input”). For data category concepts, see About data value categories. The schedule’s output and input are “Status<Type>” according to schedule component type, for example, StatusBoolean if a BooleanSchedule, StatusEnum if an EnumSchedule.
The four weekly schedule component types are:
In typical use, only outputs of schedules are linked to other components for scheduling control, such as “writable” points of the same type. Figure 313 shows a BooleanSchedule and NumericSchedule, each linked to two writable points. See Schedule component links for more details.
The BooleanSchedule is typically the most used weekly schedule. Use it directly for schedule control of BooleanWritable points (typically proxy points). If needed, it also has application for linkage to slots in extensions. For example, using an intermediate kitControl object (say, a “Not” logic-type object) use a BooleanSchedule for linkage to the Enabled slot of an alarm extension.
The EnumSchedule allows schedule control of EnumWritable points (typically proxy points). For example, link it to an EnumWritable that proxies a BACnet Multistate Output object, or to an EnumWritable that proxies a LON NVI (using an enumerated SNVT).
To properly use an EnumSchedule, first define its Facets to match those in linked EnumWritable(s).
The NumericSchedule allows schedule control of NumericWritable points (typically proxy points), which may represent setpoints, limits, or any number of other variables.