browse

6 Minute Read

| Overview

75F BMS has introduced multiple schedule states in the system. The different schedule states are introduced with the core vision of energy savings and occupant comfort in the buildings.

The following are the schedule states that are introduced:

  1. Unoccupied
  2. Occupied
  3. Preconditioning 
  4. Forced Occupied
  5. Vacation
  6. Auto Force Occupied
  7. Auto-away
  8. Emergency Conditioning
  9. Keycard Auto-Away
  10. Demand Response Occupied
  11. Demand Response Unoccupied
  12. Door/ Window Open
  13. No conditioning

For more information on the schedule, states refer to Schedules & Schedule States

The schedule states are implemented throughout the 75F BMS. The schedule states are applicable for all profiles that use the 75F CCU as an aggregator. 

| Schedule State Influencers

Influencers are nothing but factors that contribute to different schedule states' triggers.

Two types of influencers contribute to the schedule states' trigger.

  • Internal 
  • External

The table below is about different types of influencers:

 

Types of Schedules Supported in 75F

Definitions

 

Internal User Intent Set

The schedule user intents that are set by FMs, Support, End User

1

Building Schedule

 

2

Zone Schedule

 

3

Special Schedule

 

4

Named Schedule

 

5

Vacation [Building Level and Zone Level]

 

 

External Schedule Influencers

Schedule Overrides that are influenced by external triggers

6

Occupancy Sensor

 

7

Keycard Input

 

8

Door/Window Input

 

 

| Precedence Hierarchy 

Based on whether the building is unoccupied or occupied time of the actual schedule. The precedence hierarchy of the schedule states and schedule state influencers differs.

The table below provides information on that.

 Order

Priority Order

Precedence order during Occupied

Precedence order during Unoccupied

Highest

1

Demand Response Occupied

Demand Response Unoccupied

 

2

Door/Window Input

Door/Window Input

 

3

Keycard Input

Keycard Input

 

4

Auto-away

Preconditioning

 

5

Emergency Conditioning

Forced Occupied

 

6

Occupied

Auto Forced Occupied

 

7

 

Emergency Conditioning

 

8

 

Vacation

Lowest

9

 

Unoccupied

 

Schedule States Precedence Order:

Order Schedule States
Highest Occupied
  Preconditioning
  Forced Occupied
  Auto Forced Occupied
  Emergency Conditioning
  Autoaway
Lowest Unoccupied

 

| Schedule States & the Priority Levels

With the above hierarchy and precedence, the different schedule states and the influencers induce change to the desired temperatures at different level of the priority array as below.

Priority Array Level Schedule States Influencers
Level 3 Auto Away Door/Window/ Key Card/ Occupancy sensor
Level 4 Forced Occupied/ Auto Forced Occupied Door/Window/ Key Card/ Occupancy Sensor/ User Intent change
Level 8 Occupied/Unoccupied Schedules (Building/Zone/Vacation)

From the above table:

  • An Autoaway trigger induced by a door/window/key card/occupancy sensor, overrides desired temperature limits at level 8, coming from level 3 by the Autoaway setback value
  • An Auto Forced Occupied trigger induced by a door/window/key card/occupancy sensor overrides the Auto away setback or building setback temperature limits at level 8, coming from level 3 to the desired temperature limits (e.g., 70-74)
  • A Forced Occupied trigger induced by user intent, overrides the Auto away setback or building setback temperature limits at level 8, coming from level 3 to desired temperature limits (e.g., 70-74).
  • The Occupied and Unoccupied are triggered with the set schedules at level 8

| Sample Illustration of Occupancy States from Portals

Illustration 1

Corresponding Enums (using custom widgets)

Note: The Demand Response state is not a part of the Enums and it sits above all states in terms of precedence.

Illustration 2

 

Corresponding Enums (using custom widgets)

Illustration 3

Corresponding Enums (using custom widgets)

Note: The Demand Response state is not a part of the Enums and it sits above all states in terms of precedence.

| Impact of Demand Response Event

The Demand Response Event is a new type of schedule state that is introduced within the 75F system. It was a result of the Demand Response Compliance feature.

It enables 75F CCUs to balance the demand on the power grid by encouraging them to shift electricity demand to times when demand on the electric grid is lesser.​ For more information on demand response refer to Demand Response Compliance.

The Demand Response Event sits above all influencers of scheduled states.

Demand Response once triggered from the utility will be acted on top of the current state of the zone, shedding more load which it was demanding at that period of time.

The influence is reflected in the status message for the Zone, where the actual schedule state influence is appended with the Demand Response, as below.

The desired temperatures drift further away in the arc to meet the demand response requirements as below.

Note: The actual schedule state influence is still intact in the status message.

| Important points to remember

  • Door/Window Sensor input will not affect the system level functioning, but the individual Standalone Equipment alone.
  • Auto-away and auto-forced Occupied are not triggered at the same time.
  • Auto-away is not triggered during an unoccupied time.
  • Forced Occupied or Auto forced occupied are not triggered during the occupied time.

| Different Zone Level Schedule States and Effects on System Level/Building Level Schedule State

A building can have many rooms configured as zones in the 75F BMS. With all schedule states and schedule state influencers in place, it is highly unpredictable, what zone is in what schedule state and what time. Hence it is highly recommended that a facility manager understands how various combinations of the schedule states affect the building in real-time. 

The table below is about various possible combinations of schedule states that zones in the building can experience at any given point of time, and the resultant effect of it on the building.

Zone 1 Zone 2 Zone 3 Zone 4 Zone 5 Zone 6 System Status
Unoccupied Occupied Occupied Occupied Occupied Occupied Occupied
Unoccupied Occupied Occupied Occupied Occupied Occupied Occupied
Unoccupied Unoccupied Occupied Occupied Occupied Occupied Occupied
Unoccupied Unoccupied Unoccupied Occupied Occupied Occupied Occupied
Unoccupied Unoccupied Unoccupied Unoccupied Occupied Occupied Occupied
Unoccupied Unoccupied Unoccupied Unoccupied Unoccupied Occupied Occupied
Unoccupied Unoccupied Unoccupied Unoccupied Unoccupied Unoccupied Unoccupied
Forced Occupied Unoccupied Unoccupied Unoccupied Unoccupied Occupied Occupied
Forced Occupied Occupied Occupied Unoccupied Unoccupied Unoccupied Occupied
Forced Occupied Forced Occupied Occupied Occupied Unoccupied Unoccupied Occupied
Forced Occupied Forced Occupied Forced Occupied Occupied Occupied Occupied Occupied
Forced Occupied Forced Occupied Forced Occupied Forced Occupied Occupied Occupied Occupied
Forced Occupied Forced Occupied Forced Occupied Forced Occupied Forced Occupied Occupied Occupied
Forced Occupied Forced Occupied Forced Occupied Forced Occupied Forced Occupied Forced Occupied Forced Occupied
Auto Forced Occupied Occupied Occupied Occupied Occupied Occupied Occupied
Auto Forced Occupied Occupied Occupied Occupied Unoccupied Unoccupied Occupied
Auto Forced Occupied Auto Forced Occupied Occupied Occupied Occupied Occupied Occupied
Auto Forced Occupied Auto Forced Occupied Auto Forced Occupied Occupied Occupied Occupied Occupied
Auto Forced Occupied Auto Forced Occupied Auto Forced Occupied Auto Forced Occupied Occupied Occupied Occupied
Auto Forced Occupied Auto Forced Occupied Auto Forced Occupied Auto Forced Occupied Auto Forced Occupied Unoccupied Auto Forced Occupied
Auto Forced Occupied Auto Forced Occupied Auto Forced Occupied Auto Forced Occupied Auto Forced Occupied Auto Forced Occupied Unoccupied
Vacation Occupied Occupied Occupied Occupied Occupied Occupied
Vacation Occupied Occupied Occupied Occupied Occupied Occupied
Vacation Vacation Occupied Occupied Occupied Occupied Occupied
Vacation Vacation Vacation Occupied Occupied Occupied Occupied
Vacation Vacation Vacation Vacation Occupied Occupied Occupied
Vacation Vacation Vacation Vacation Vacation Unoccupied Unoccupied
Vacation Vacation Vacation Vacation Vacation Vacation Vacation
Preconditioning Occupied Occupied Occupied Occupied Occupied Occupied
Preconditioning Occupied Occupied Occupied Occupied Occupied Occupied
Preconditioning Preconditioning Occupied Occupied Occupied Occupied Occupied
Preconditioning Preconditioning Preconditioning Occupied Occupied Occupied Occupied
Preconditioning Preconditioning Preconditioning Preconditioning Occupied Occupied Occupied
Preconditioning Preconditioning Preconditioning Preconditioning Preconditioning Occupied Occupied
Preconditioning Preconditioning Preconditioning Preconditioning Preconditioning Preconditioning Preconditioning
Preconditioning Occupied Vacation Occupied Occupied Occupied Occupied
Autoaway Occupied Occupied Occupied Occupied Occupied Occupied
Keycard Autoaway Preconditioning Occupied Occupied Occupied Occupied Occupied
Door Open Autoaway Forced Occupied Occupied Occupied Occupied Occupied
Forced Occupied Keycard Autoaway Preconditioning Autoaway Occupied Occupied Occupied
Preconditioning Door Open Preconditioning Keycard Autoaway Auto Forced Occupied Occupied Occupied
Vacation Unoccupied Vacation Door Open Preconditioning Auto Forced Occupied Occupied
Autoaway Occupied Occupied Occupied Occupied Occupied Occupied
Autoaway Occupied Door Open Preconditioning Keycard Autoaway Occupied Occupied
Autoaway Autoaway Occupied Door Open Preconditioning Keycard Autoaway Occupied
Autoaway Autoaway Autoaway Occupied Occupied Occupied Occupied
Autoaway Autoaway Autoaway Autoaway Occupied Occupied Occupied
Autoaway Autoaway Autoaway Autoaway Autoaway Occupied Occupied
Autoaway Autoaway Autoaway Autoaway Autoaway Autoaway Autoaway
Keycard Autoaway Occupied Occupied Occupied Occupied Occupied Occupied
Keycard Autoaway Occupied Occupied Door Open Preconditioning Keycard Autoaway Occupied
Keycard Autoaway Keycard Autoaway Occupied Occupied Occupied Occupied Occupied
Keycard Autoaway Keycard Autoaway Keycard Autoaway Occupied Occupied Occupied Occupied
Keycard Autoaway Keycard Autoaway Keycard Autoaway Keycard Autoaway Occupied Occupied Occupied
Keycard Autoaway Keycard Autoaway Keycard Autoaway Keycard Autoaway Keycard Autoaway Occupied Occupied
Keycard Autoaway Keycard Autoaway Keycard Autoaway Keycard Autoaway Keycard Autoaway Keycard Autoaway Keycard Autoaway
Door Open Occupied Occupied Occupied Occupied Occupied Occupied
Door Open Occupied Door Open Preconditioning Keycard Autoaway Occupied Occupied
Door Open Door Open Occupied Door Open Preconditioning Keycard Autoaway Occupied
Door Open Door Open Door Open Occupied Occupied Occupied Occupied
Door Open Door Open Door Open Door Open Occupied Occupied Occupied
Door Open Door Open Door Open Door Open Door Open Occupied Occupied
Door Open Door Open Door Open Door Open Door Open Door Open Occupied
Emergency Conditioning Occupied Occupied Occupied Occupied Occupied Emergency Conditioning
Emergency Conditioning Occupied Door Open Preconditioning Keycard Autoaway Occupied Emergency Conditioning
Emergency Conditioning Door Open Occupied Door Open Preconditioning Keycard Autoaway Emergency Conditioning
Emergency Conditioning Door Open Door Open Occupied Occupied Occupied Emergency Conditioning
Emergency Conditioning Door Open Door Open Door Open Occupied Occupied Emergency Conditioning
Emergency Conditioning Door Open Door Open Door Open Door Open Occupied Emergency Conditioning
Door Open Emergency Conditioning Preconditioning Keycard Autoaway Keycard Autoaway Occupied Emergency Conditioning

| Impact of Multi-Module

Multi-module is a state when more than one device or profile is paired within a zone, the 75F system supports up to 3 modules (Device/ profile) (System influenced / Standalone) to be paired within a zone.

At any point in time in a multi-module zone, all the modules within the zone will have the same schedule state, and the same is indicated on the zone level.

In CCU

In Portals

Any external schedule influencers 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.

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