browse

| Introduction

Building schedules act as time limits and are acting as constraints in temperature settings by impeding zone-level operations by posing validations when there are new schedules being applied with deadbands, setbacks & desired temperatures on the zone level.

To curb this, Building Occupancy is introduced which provides the occupied time and unoccupied time for a building at a zone level. This helps the Facility Managers to set zone level limits for specific zones without having to worry about validations and limits across the system, mostly on the master controller level. 

Note: If the user is moving to the latest V2 scheduler, then the building schedule that was available for the existing site would be copied and created as a Temporary Building Named schedule in the new version. This is effectively a named schedule that would have all the user limits, deadbands, setback copied from the building tuners and made available with the above created temporary building named schedule.

| Accessing the Building Occupancy

  • Log in to Internal Portal
  • The Heatmap page is displayed.

191.png

  • Select the Building Occupancy from the dropdown.

192.png

  • The Building Occupancy is displayed.

193.png

| Editing & Deleting an Occupancy

The building occupancy displays occupied and unoccupied legends which are indicative of the building occupancy.

193.png

  • Click the Edit Occupancy option to edit the occupancy time slot. For more information on validations regarding building occupancy please refer to Scheduler Validations.

Occupancy-1.png

  • Hovering over the time slot displays the occupancy state (occupied or unoccupied) and time of the building.

azopiuy67b.png

Unoccupied.png

 

  • The occupancy component displays an interval of 15 minutes for every time slot which is indicative of the occupancy component when the user drags the cursor to select a time slot.

15 minutes.png

  • The user can hover on the left or right edge of an occupied time slot and select the cursor to increase or decrease the time slots.

drag and drop.png

 

  • Click on an occupied time slot to display the delete option of a specific occupied time slot.

Delete11.png

  • Click on Delete delets1.png to delete the occupied time slot.

delete message.png

  • The occupied time slot is deleted.

1d1.png

 

1d2.png

  • Multiple time slots ranging across multiple days can be created by holding the Shift+ Left Click button and dragging the cursor across the occupancy table.

1d3-1.png

  • Multiple time slots ranging across multiple days can be deleted by holding the Ctrl+ Left Click button.

Multiple Time Slots.png

  • Click on Delete delets1.png to delete the selected occupied time slots.

 

1d3.png

  • Click Delete to confirm and delete the occupancy for multiple time slots across multiple days.

When the occupied slots are extended for building occupancy, then the time tool tip will be displayed over the cursor tool tip for the occupied time slot.

591c9cc4-0075-4f3d-9389-0707e8c08727.png

| Extending or Trimming Time Slots

Multiple occupied time slots can be extended or trimmed by clicking Ctrl+Left Click and selecting the time slots and dragging the cursor for one timeslot. The changes are reflected in the rest of the selection.

  • Select the Time Slots to be edited.

step 1.png

  • Extend or trim the time slot for one of the time slots selected.

Step 2.png

The same changes are reflected in the rest of the selection.

Step 3.png

Note: The changes reflected will be similar to the change made in one selection in terms of similar time intervals. For example, if a time slot is extended or trimmed by 30 minutes, then a similar change of 30 minutes will be reflected for the rest of the slots.

| Partial & Complete Overlap

Occupied slots can be drawn over other occupied slots if all the slots are overlapped completely in the selection.

  • Drag the cursor to overlap the occupied time slots.

Step 24.png

The unoccupied slots are completely overlapped.

step 25.png.

On the contrary, partially drawing the cursor and overlapping over occupied time slots will result in an error pop up.

  • Drag the cursor partially to overlap the occupied time slots.partial.png

An error message is displayed.

partial 2.png

| For CCU & Portals

The building occupancy in CCU follows all the interactivity conditions as above.

  • Select the Building Occupancy from the Building Tab

GetImage (7).png

  • Click the Add button to add Building Occupancy

GetImage (7).png

  • Add the desired Start Time and End Time from the dropdown and the day/days of the week.

GetImage (8).png

  • Click Add to Add the Building Occupancy.

Note:  When a new site is registered via a new CCU, the occupancy is considered from 00.00 to 24.00 all days of the week by default.

Note: The rest of the interactivity validations remain the same for the building occupancy across portals.

| Force Trimming in Building Occupancy

There are certain cases to be taken into consideration while force-trimming building occupancy for schedules and their corresponding schedule groups. They are as follows:

Case 1: All zones are following zone schedule: Let us consider a scenario where all zones are following a zone schedule. In this case, the force trimming will be allowed as per the schedule group assigned to the schedule.

Screenshot 2024-09-02 162228.png

(a) Everyday:

(i) If the schedule follows the Everyday schedule group, and Monday is force-trimmed from the group, then the entire group will be defined as unoccupied.

(ii) If the schedule follows the Everyday schedule group, and the time period occupied is from 8:00 AM to 5:30 PM, and 12:00 AM to 12:00 PM is force-trimmed from Monday, then 12:00 AM to 12:00 PM will be defined as unoccupied, whereas 12:00 PM to 5:30 PM will be defined as occupied.

(b) Weekday+Weekend:

(i) If the schedule follows the Weekday+Weekend schedule group, and Monday is force-trimmed from the group, then the entire weekday will be defined as unoccupied, whereas the weekend will remain occupied.

(ii) If the schedule follows the Weekday+Weekend schedule group, where the time period occupied is 8:00 AM to 5:30 PM, and 12:00 AM to 12:00 PM is force-trimmed from Monday, then 12:00 AM to 12:00 PM will be defined as unoccupied, whereas 12:00 PM to 5:30 PM will be defined as occupied for the weekday schedule, but no change will occur for the weekend schedule.

The same will be observed in cases where Saturday (a day in the weekend schedule) is force-trimmed from the schedule group, but no change will occur in the weekday schedule group.

(c)  Weekday+Saturday+Sunday:

(i) If the schedule follows the Weekday+Saturday+Sunday schedule group, and Monday is force-trimmed from the group, then the entire weekday will be defined as unoccupied, whereas no change will occur for Saturday and Sunday.

(ii) If the schedule follows the Weekday+Saturday+Sunday schedule group, where the time period occupied is from 8:00 AM to 5:30 PM, and 12:00 AM to 12:00 PM is force-trimmed from Monday, then 12:00 AM to 12:00 PM will be defined as unoccupied, whereas 12:00 PM to 5:30 PM will be defined as occupied for the weekday schedule, but no change will occur for Saturday or Sunday.

The same will be observed in cases where Saturday or Sunday is force-trimmed from the schedule group, but no change will occur in the weekday schedule group.

(d) 7 Day:

(i) If the schedule follows a 7-day schedule group, and Monday is force-trimmed from the group, then Monday will be defined as unoccupied without any change to the rest of the days.

(ii) If the schedule follows the 7-day schedule group, where the time period occupied is defined from 8:00 AM to 5:30 PM, and 12:00 AM to 12:00 PM is force-trimmed from Monday, then Monday will be defined as unoccupied from 12:00 AM to 12:00 PM, whereas 12:00 PM to 5:30 PM will remain occupied without any change to the rest of the days.

Case 2: All zones are following named schedule: Let us consider a scenario where all zones are following a named schedule. In this case, force-trimming won’t be applicable, but the user will have an option to go back and re-edit the building occupancy.

Screenshot 2024-09-02 163309.png

Case 3: All zones are following a combination of zone and named schedule: Let us consider a scenario where all zones are following a combination of zone schedule and named schedule. In this case, force-trimming won’t be applicable, but the user will have an option to go back and re-edit the building occupancy.

Screenshot 2024-09-02 163924.png

Special Cases:

1. Let us consider a scenario for a college following a zone schedule, where building occupancy is defined for a 7-day schedule group, out of which Monday to Friday is occupied. In this case, if a user attempts to change the schedule group from the 7-day schedule group to any other group (e.g., Weekday+Weekend, Everyday, Weekday+Saturday+Sunday), then such a group change will only be allowed for Weekday+Weekend and Weekday+Saturday+Sunday since the building occupancy is defined only from Monday to Friday.

2. Let us consider a scenario for a salon following a zone schedule, where building occupancy is defined for a 7-day schedule group, out of which Monday to Saturday is occupied with the exception of Sunday having occupancy till 2:00 PM. In this case, if the user attempts to change the schedule group to any other group (e.g., Weekday+Weekend, Everyday, Weekday+Saturday+Sunday), then such a group change will be allowed for all the schedule groups but will be defined as unoccupied from 2:00 PM to 5:30 PM for either Everyday, Weekday+Weekend, or Weekday+Saturday+Sunday schedule group.

3. Let us consider a scenario for a hospital building following a zone schedule, where building occupancy is defined for a 7-day schedule group, where all the days are occupied 24x7. In this case, if the user attempts to change the schedule group to any other group (e.g., Weekday+Weekend, Everyday, Weekday+Saturday+Sunday), then such a group change will be allowed for any group since the building occupancy is defined for all seven days of the week.

Previous
Next

Comments

0 comments

Please sign in to leave a comment.

Was this article helpful?

0 out of 0 found this helpful
Powered by Zendesk