©2025 Copeland LP.
026-1803 R13 Supervisor I&O User Guide 9 - 23
• END DATE - the date the maintenance override should
end in this field. If the maintenance override is only going
to last one day, enter the same date in this field as is in the
Start Date.
• END TIME - the end time at which the Time Schedule will
stop following the maintenance override and start using
its standard events. If you want the maintenance override
to be followed for the entire day, leave this field set to
23:59 and the Start Time to 0:00.
• ON EVENT TIME - The time of day you wish the schedule
output to be ON when the Time Schedule application is
following this maintenance override.
• OFF EVENT TIME - The time of day you wish the
schedule output to be OFF when the Time Schedule
application is following this maintenance override.
Once the maintenance schedule is complete (moved past
the END DATE), the schedule application returns to
following its standard schedule. Maintenance Schedule is
active for the entire day and for all days between (and
including) the START DATE and END DATE.
9.14.5 Maintenance Overrides
Maintenance overrides are set up through Time
Scheduling. Time Schedules are used for timed activation
and deactivation of loads and for providing occupied and
unoccupied building times for occupancy-driven systems
(such as Sensor Control, Lighting, and HVAC).
There are four different types of schedules used:
• Master schedules are the main scheduling unit. A master
schedule consists of up to 15 scheduled ON/OFF event
pairs, which may be programmed to occur on any
individual date and time or series of dates and times.
Master schedules may also drive slave schedules.
• Slave schedules are similar to master schedules, except
their operation is driven by a master schedule. Slave
schedules, generally, are alterations of the master
schedule’s event times. The ON/OFF times in a slave
schedule may take place either at specific defined times
of the day or relative to the times given in the master
schedule. For example, a master schedule may say: “The
building is occupied from 8:00 a.m. to 9:00 p.m.,” while
one of its slave schedules says “Dim the building lights 15
minutes before the store closes.” Slave schedules may
also be mastered by other slave schedules to create a
series of stacked schedules.
• Holiday schedules are used to tell master and slave
schedules that a special day or event is occurring. For
example, master schedules and their corresponding
slave schedules may be programmed with special
holiday events, such as “Keep all lights off during Holiday
x.” The holiday schedule’s job is to inform the schedules
to which it is connected, “Today is Holiday x.” Although
holiday schedules are used exclusively by Time
Scheduling applications, they are set up as individual
applications separate from Time Scheduling.
• Maintenance schedules are not schedules but
Maintenance Override functions that may be made to
exist within an individual master or slave schedule.
Maintenance schedules are used to override the ON/OFF
instructions of an individual master or slave schedule
temporarily. Generally, maintenance schedules are only
used for one-shot applications, such as keeping the lights
on an extra hour for a single night. Maintenance
schedules override all other events within a master or
slave schedule, including holidays.
How Schedules Work Events
Master schedules and slave schedules consist of up to 15
pairs of events. Events are simple commands to turn the
schedule output either ON or OFF at a particular time within a
range of days. Events are usually programmed in pairs, so that
during a specified range of days the schedule output can be
turned ON and OFF at a particular time within the same day.
However, events may be programmed singularly (one OFF or
one ON command per day). Events may be programmed to
take place on any or all days from Sunday to Saturday. In
addition, events may take place on any or all of four holiday
(or “special”) dates, called HD1, HD2, HD3, and HD4. Holiday
schedules are used to tell the master or slave schedules
when these special dates occur.
Absolute and Relative Events
Master schedule events always occur at specific times of the
day. In other words, when you program an event pair in a
master schedule, you must specify two specific times of the
day the events will occur. These types of events are called
absolute events.
However, when programming event times in slave schedules,
you may choose to enter event times that are relative to its
master schedule’s ON and OFF times. These types of events
are called relative events. They are programmed not as
absolute times but as amounts of time before or after its
master schedule’s events.
NOTE
NOTE: Note that the End Time is not the time you
wish for the Time Schedule to make a state
transition, it is the time when you want to end the
schedule override.