A zone represents a single thermal space or logical control group within the system. Typically, a zone corresponds to a relatively small physical space (such as an office, meeting room, or retail section) where a single temperature setpoint and schedule are configured and managed by the user.
In some scenarios, however, the space may be large or served by multiple pieces of equipment - a single controller may not be sufficient.. In such cases, multiple edge controllers (modules) may be deployed within the same zone to control different pieces of equipment serving that space.
Some sample spaces that this configuration is useful :
Open offices
Auditoriums
Retail floors
Gymnasiums
Warehouses
Airport halls
In these cases, to serve the multi equipments in these spaces - each edge controller manages one piece of equipment for conditioning the space, while all controllers operate under the same zone-level settings :
- Temperature setpoints
- Conditioning mode (heating, cooling, auto, off)
- Fan mode for standalone equipment
- Schedules
- Occupancy states
Impact of Multi-Module across portals, apps and CCU
Multi-Module is a configuration in which more than one device is paired within a zone. The 75F system supports up to 3 modules per zone currently. These may be paired as a device profile (e.g., DAB Zone), a system influencing profile (e.g., OTN), or a standalone profile (e.g., Hyperstats, MyStat). Multiple profiles may be used within one zone.
In CCU multiple modules can be added as shown below.
A maximum of 3 modules per zone can be added.
In Multi-Module zones, all of the modules will have the same schedule state, which is indicated on the zone screen on the CCU and in Facilisight.
In Portals
Any external schedule influence once triggered will be influencing the entire zone, irrespective of whether the other modules are enabled via configuration for that state.
Once the schedule state is consumed by the zone from the module of the highest rank in the multimodule, then the desired temperatures are inherited by other modules in the multimodule zone.
The table below is about various possible combinations of schedule states that a multi-module zone in the building can experience at any given point of time, along with the zone status and Desired temperatures.
| Scenario | Module 1 | Module 1 | Module 2 | Module 2 | Module 3 | Module 3 | Zone | Zone |
| State | Desired Temperature | State | Desired Temperature | State | Desired Temperature | State | Desired Temperature | |
| Initial | Occupied | 70/74 | Occupied | 70/74 | Occupied | 70/74 | Occupied | 70/74 |
| Trigger | Door/Window Open | 70/74(Stop conditioning) | Occupied | 70/74 | Occupied | 70/74 | Door/Window Open | 70/74 (Stop conditioning) |
| Result | Door/Window Open | 70/74(Stop conditioning) | Door/Window Open | 70/74(Stop conditioning) | Door/Window Open | 70/74(Stop conditioning) | Door/Window Open | 70/74(Stop conditioning) |
| Trigger | Keycard AutoAway | 68/76 | Occupied | 70/74 | Occupied | 70/74 | Keycard AutoAway | 68/76 |
| Result | Keycard AutoAway | 68/76 | Keycard AutoAway | 68/76 | Keycard AutoAway | 68/76 | Keycard AutoAway | 68/76 |
| Trigger | AutoAway | 68/76 | Occupied | 70/74 | Occupied | 70/74 | AutoAway | 68/76 |
| Result | AutoAway | 68/76 | AutoAway | 68/76 | AutoAway | 68/76 | AutoAway | 68/76 |
| DR Active | DR Occupied | 66/78 | DR Occupied | 66/78 | DR Occupied | 66/78 | DR Occupied | 66/78 |
Note: A CCU operates according to a time zone that is set during the CCU registration process. If there are any changes to the time zone, the set schedule will be altered according to the time zone set. Therefore, it is recommended to restart the application whenever the time zone is modified to ensure the schedule remains accurate and the system functions correctly.
Comments
0 comments
Please sign in to leave a comment.