9.6. Schedules
A schedule works by implementing the selected control on tagged nodes for the floors specified in the control rules. For a schedule to run, here are a few important things to help understand how schedules operate are
To implement control on specific Response Nodes they must be tagged from the Response Node’s menu
If no Response Nodes are selected, it will be implemented to all the Response Nodes for the selected floor
If no Response Nodes and no floors are selected, it will be implemented for all the Response Nodes in the whole building
At the start of the schedule, the control command is sent and the same goes for when any transition is made i.e. pausing a schedule, resuming a schedule, or force starting it. However, if a schedule is created that started in the past, no command will be sent unless the starting time arrives if the schedule is activated.
At the end of the schedule, to go back to previous settings, the “recall settings“ command is sent. It is important to note that since this is a recall setting it would take them back to the last saved settings. If a configuration is not saved properly and a schedule is run it can go back to its factory default operations. It is always recommended to save settings when configurations are done via the smartphone Apps.
9.6.1. Rules
Each schedule can have as many rules as necessary with the ability to choose from a range of configuration changes that are required to run on specific time from above and beyond the automatic operation of LCS. Each Rule is defined by the following:
Set max, min or low lights to
available lighting output percentages ranging from 0% to 100%
Set Dwell or low light Time
available times from 1 minute up to 60 minutes
Set Personality to from the whole range of profiles available to OR lighting control system
Set Scenes to one of the eight scenes available in OR-enabled LCS.
For: here, the user can pick tags accessible to them created & assigned earlier in the Response Node’s menu
On: allows users to pick a floor where they wish for this rule to be implemented
9.6.2. Schedules Settings
Each schedule can be custom named to run these temporary time-based settings weekly or on a specific day and time in the future. Based on the requirement users can choose one of the mode of operations mentioned below;
9.6.2.1. Weekly Schedule
This mode of operation gives you the ability to create schedules on a weekly basis. An example of a weekly schedule is as below:
You can achieve the intended outcome from the schedule “Test Schedule” following the control philosophy as below;
During 08:00 am to 18:00 pm on Monday to Friday
Set max light for “open office” tagged Response Nodes to 70% on Level 1
Set max light for “corridor” to 40% on floor 2
Set max light for “meeting room” tagged Response Nodes to 70% on Level 1
You may also add another rule where “security light” tagged luminaires were to stay 10% on the same floor to enable enough illumination for security in corridor area etc…
User can add as many schedules as required to achieve intended outcomes. In the end you can measure the energy efficiency from your schedule based upon your timed operation for any space.
9.6.2.2. Set date and time
The date and time mode allows you to choose the exact day in the future when you want your schedule to run, and when it should end. Within the schedule you now have the ability to select this mode by clicking on “date and time“ once you create a new schedule.
You can achieve the intended outcome from the schedule “Test Schedule” following the control philosophy as below;
During 08:00 am to 18:00 pm on 17th of July 2021
Set max light for “open office” tagged Response Nodes to 70% on Level 1
Set max light for corridor to 40% on Level 1
Both types of schedules can be created and coexist next to each other. Just make sure that when you have multiple overlapping schedules for your building, that you order them based on their priority.
It is also worth mentioning that within a schedule;
A rule should be implemented for one tag & if same control is to be implemented to multiple spaces then either create a common tag for those areas or generate multiple rules i.e. one for each tag. An example is shown above in figure 1 where 70% is the max light for both open office and meeting room by creating two separate rules.
If there are conflicting rules for a tag, then the rule on top would take precedence over the ones lower.
If a rule is created with multiple tags, then it would only be implemented to only those Response Nodes that have all those tags assigned to it and not to all the Response Nodes. For example, see the below explanation;
GROUP 1: Response Nodes A, B & C are assigned to “Corridor” tag.
GROUP 2: Response Nodes D, E & F are assigned to “Open Office” tag.
GROUP 3: Response Nodes G, H & I are assigned both tags “Corridor” and “Open Office”.
Now if in a rule we select “Corridor” & “Open Office” to go to “off scene” then only group 3 would respond to that schedule as that is the only group that has both tags at the same time. They work the same with tenant tags.
9.6.3. Schedules Statuses
After setting up the schedule and clicking on “Save Schedule” (or pressing the “Play” button), the schedule will start running but the rule will take effect on Response Nodes only at the beginning of the time window selected for this schedule.
The schedule can be in one of 3 different states;
9.6.3.1. “Inactive” state
Inactive means that the schedule is running but is waiting for the selected time window in order to be activated. Once the time window started, the schedule will be in “Active” state.
9.6.3.2. “Active”
Active means that the schedule is currently running and the rule has been applied to the Response Nodes (i.e. the selected time window has started). You can always pause any active schedule by pressing the “Pause” button.
9.6.3.3. “Always Active”
Always active means that the rule will apply immediately on Response Nodes regardless of the time window selected on the schedule and it will remain active until you pause it or delete the schedule. Always active can be enabled by pressing the icon inside the red square showing in the below picture.