Most standard applications use the Occupancy Mode Determination module which can make use of up to four different occupancy inputs. These inputs (Occupancy Override, Temporary Occupancy, Occupancy Schedule, and Occupancy Sensor) from highest to lowest priority are used to determine the effective occupancy used by other modules throughout the application.
The following example illustrates the common use of the various inputs:
A particular system is responsible for maintaining temperature control of a large conference room. The output of this module, Effective Occupancy, is used by other modules in determining the effective setpoint. You can use Occupancy Override to perform manual control of the Occupancy Mode. The building schedule dictates the Occupancy Schedule input for daily Occupied/Unoccupied operation. The room has an Occupancy Sensor to allow the system to use the Standby heating and cooling setpoints and lower outdoor air requirements if the room is not being used during scheduled Occupied hours. Finally, the room has a Temporary Occupancy push-button on the local zone temperature sensor to allow the occupants to activate Occupied temperature control after normal business hours.
See the Primary States (Occupancy Mode Determination) section for a detailed description of the interaction between these inputs in determining the effective occupancy.
You cannot view or modify the modules in this group’s logic.