Exception Schedule - Metasys - LIT-1201793 - Software Application - Site Management Portal - 12.0.50

Metasys Site Management Portal Help

Product name
Site Management Portal
Document type
User Guide
Document number
Revision date

The exception schedule provides a list of exceptions to the weekly schedule. Exceptions define a different set of events that supersede the events for particular days in the weekly schedule. An exception can be defined for a date, a date range, a week and day, or a reference to a Calendar. The following table contains information on the four types of exceptions. Wild cards can also be used to define exceptions; see Wildcards for more information.

Table 1. Exception Types

Exception Type



Occurs on a specific date.

Date Range

Occurs during a range of dates.

Week and Day

Occurs on certain weekdays during certain weeks of certain months. For example, the second Tuesday in any month or any Wednesday in June.

Calendar Reference

Occurs during all dates selected in the referenced calendar. Associating an exception with a calendar allows you to reference a large number of dates.

Note: The N1 exception schedule only supports the Date exception. For example, to schedule the same exception 3 days in a row using an N1 Exception schedule requires the use of three separate date exception entries. Date range, week and day, and calendar reference exceptions are not supported.

Each exception can have one or more events that run during the exception time period. Recall the example in the Schedule topic where you scheduled a fan to start at 7:00 and stop at 22:00 on all Mondays. You can create a date type exception to this weekly schedule if you want the fan to start and stop at different times on a certain day. For example, you can create an exception for Monday, May 26, and define an Off event at the start of the day (00:00), an On event at 9:00 in the morning (instead of 7:00), and another Off event at 17:00 in the evening (instead of 22:00). If you do not define the Off event at 00:00, the Weekly Schedule takes effect between 00:00 and 09:00, and the fan turns on at 07:00 as originally scheduled.

You can assign a precedence level (1–16, where 1 receives the highest precedence) to each exception, regardless of type, to determine the order of execution. If you define two or more exceptions for the same date, the exception with the highest precedence executes. For example, an exception with a precedence of 2 executes over an exception with a precedence of 8 if they are both defined for the same date.

If all exceptions for the same date have the same precedence, the exception that appears first in the exception list executes first; therefore, if you have multiple exceptions defined for one day, the exceptions apply by precedence level and then by the order of the items in the exception list.

Double clicking the exception schedule allows you to edit the exception schedule.

The JCI Exception Schedule attribute for the engine object (also an FAC mapped to an engine) allows you to set how long exception schedules are kept after the exception date has expired. The default value is Auto Delete 31 days. Two options, Auto Delete 7 days and Manual Delete are available for this attribute. See the JCI Exception Schedule attribute configuration in the Engine Device Object section for more information.

Note: Manual Delete is needed for locations like Japan where the local standards state that only the BACnet workstation can delete exception schedules.