The present application is related to U.S. patent application Ser. No. 12/260,046, filed Oct. 28, 2008, entitled “A Building Management Configuration System”. U.S. patent application Ser. No. 12/260,046, filed Oct. 28, 2008, is hereby incorporated by reference.
The invention pertains to schedules and particularly to making additional schedules relating to the aforementioned schedules. More particularly, the invention pertains to schedules for various components of a building.
The invention is an approach for deriving additional schedules from a master schedule but with different scheduled-on time periods. The additional schedules may be shifted master or reference schedules. The scheduled-on and scheduled-off periods of the reference schedule may be shifted for the additional schedules. The reference schedule may have special events which may have their own scheduled-on and scheduled-off periods which may override the scheduled-on and scheduled-off periods of the day to which the special event is assigned. The scheduled-on and scheduled-off periods of the special events may be shifted for the shifted schedules.
In building automation systems, there is a desire to manage system control activities with a single master weekly schedule. Zones or equipment could then be controlled by creating shifted schedules which shift the time-of-day events of the master schedule. The overhead and complexity of system management and maintenance can be greatly reduced. Changes in occupancy or hours of operation may be implemented by adjusting just the master schedule.
The present approach relates to a building control system (“BCS”) built upon a NiagaraAX™ (NiagaraAX or Niagara) Framework™ (framework) by Tridium, Inc. The NiagaraAX framework may provide a set of weekly schedule components. A weekly schedule may define a sequence of repeating time-of-day events for each day of the week as well as exceptions to the normal weekly schedule (called “special events”).
System control activities (i.e., lights on/off, air conditioning on/off) may then be managed by creating schedules which shift the time of day events of the master schedule. System management may be much simpler when changes to the building's hours of operation are implemented by editing or shifting just the master schedule. The shifted schedules may simply apply their shifts to an updated master schedule.
The building control system may be configured with multiple zones. For example, a zone may be a department within a large retail store. Each zone may include heating, ventilation and air conditioning (“HVAC”) equipment and lighting controls. To efficiently manage the building's energy usage, temperature setpoints and lights in each zone may be controlled separately. Additionally, the controls should be scheduled based on the building's operating mode. The store may be open for business from 8:00 AM until 8:00 PM; however, employee-specific zones may be in use before and after normal store hours.
In an existing building control system, a weekly schedule may be created for each zone. The schedule may be customized to the zone's usage. Areas open to the public may be scheduled-on or open during normal operating hours and scheduled-off or closed outside normal operating hours. Employee-specific areas may be scheduled-on earlier and later times than those of the public areas. For safety reasons, parking lot lights should be scheduled to be on prior to the store opening and stay on for a period after the store closes. Therefore, parking lot lights require a weekly schedule that needs to be managed. Any time that there is a change in occupancy or hours of operation, multiple weekly schedules need to be manipulated. As a building size grows and the mixed usage of building space increases, the complexity and overhead of managing and controlling schedules may increase.
With the present approach, a single master weekly schedule may be defined for the building. To control each zone, separate shifted schedules may be established. These separate schedules may control setpoints and lighting by shifting the on-to-off and off-to-on transitions of the master schedule. For instance, the normal weekly schedule for Monday may transition from off-to-on at 8:00 AM and transition from on-to-off at 8:00 PM. A shifted schedule for an employee mode may need to, for example, transition from scheduled-off to scheduled-on one hour earlier and transition from scheduled-on to scheduled-off one hour later. The employee mode schedule may be assigned to employee specific zones within the building such as the warehouse and break room. The complexity and overhead of schedule management and control may be greatly reduced. Again, a change in occupancy or hours of operation may be implemented by adjusting just the master schedule.
The present approach has two kinds of shifted schedules. A first kind is a ShiftedSchedule (shifted schedule) which provides a single set of off-to-on and on-to-off shifts. These shifts may be applied to every day of the week and special events. The second kind is a DailyShiftedSchedule (daily shifted schedule) which provides a set of separate off-to-on and on-to-off shifts for each day of the week and for special events. That is, there may be more than one set of shifts for the week with the second kind of shifted schedule and one set of shifts with the first kind of shifted schedule.
The NiagaraAX framework may provide four types of weekly schedule components. These types of components may vary by data value. The data values for these types may include Boolean, numeric, enumeration and string. Shifted schedule and daily shifted schedule types may be implemented for each of the weekly schedule types. The examples described herein are of the Boolean type for illustrative purposes; however, these examples may be described in terms of a numeric, enumeration or string type of data values.
One approach may be illustrated with examples described herein which invoke components for the Boolean weekly schedule type. These components may be referred to as a BooleanShiftedSchedule (shifted schedule) and a BooleanDailyShiftedSchedule (daily shifted schedule).
Details of schedules 13 are shown in a portion 17 of screen 11. Information about the Boolean shifted schedule is shown in block 18, and information about Boolean daily shifted schedule is shown in block 19. Also, details of BooleanSchedule01 and BooleanSchedule02 (regular or master schedules) are shown in blocks 21 and 22, respectively.
Applying Boolean logic to scheduling, the schedule state may be said to be true during a “scheduled-on” period and false during a “scheduled-off” period. When transitioning from a scheduled-off period to a scheduled-on period, the transition is from false to true. Similarly, when transitioning from a scheduled-on period to a scheduled-off period, the transition is from true to false.
The Boolean daily shifted schedule may have a regular NiagaraAX Boolean schedule with the following additional properties as highlighted by rectangle 26 in presentation 25 of screen 11 shown in
One approach for schedule shifting may be made as in the following. A master or regular weekly schedule 31 may be created by clicking on item 32 of Nav portion 12 and on tab 29 at the bottom of schedule 31, as shown in screen 11 of
A shifted schedule presentation 23 may then be added by clicking on item 27 in Nav portion 12 of screen 11 in
In presentation 31 of
A daily shifted schedule may be effected. To configure the component, one may select a regular schedule as the reference schedule, set the update time, and assign false-to-true and true-to-false shift values for each day of the week and for special events in a single presentation of screen 11.
A diagram of screen 11 in
In the illustrative example shown in
In sum, the shifted schedule described herein shows a presentation with one set of settings which may be applied separately to each day of the week and each special event, whereas the daily shifted schedule may be applied simultaneously to all days of the week and special events which can have different shift settings for each day and special events.
At the programmed update frequency or by user triggered action, the daily shifted schedule may apply the appropriately defined set of false-to-true and true-to-false shifts to the time-of-day events for each day of the week and special events of the reference schedule. The results of the defined set in rectangle 48 of presentation 47 in
In the present specification, some of the matter may be of a hypothetical or prophetic nature although stated in another manner or tense.
Although the present system has been described with respect to at least one illustrative example, many variations and modifications will become apparent to those skilled in the art upon reading the specification. It is therefore the intention that the appended claims be interpreted as broadly as possible in view of the prior art to include all such variations and modifications.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4375637 | Desjardins | Mar 1983 | A |
| 4816208 | Woods et al. | Mar 1989 | A |
| 5042265 | Baldwin et al. | Aug 1991 | A |
| 5161387 | Metcalfe et al. | Nov 1992 | A |
| 5385297 | Rein et al. | Jan 1995 | A |
| 5390206 | Rein et al. | Feb 1995 | A |
| 5768119 | Havekost et al. | Jun 1998 | A |
| 5929761 | Van der Laan et al. | Jul 1999 | A |
| 5946303 | Watson et al. | Aug 1999 | A |
| 5955946 | Beheshti et al. | Sep 1999 | A |
| 6124790 | Golov et al. | Sep 2000 | A |
| 6178362 | Woolard et al. | Jan 2001 | B1 |
| 6185483 | Drees | Feb 2001 | B1 |
| 6223544 | Seem | May 2001 | B1 |
| 6295526 | Kreiner et al. | Sep 2001 | B1 |
| 6295527 | McCormack et al. | Sep 2001 | B1 |
| 6314328 | Powell | Nov 2001 | B1 |
| 6351213 | Hirsch | Feb 2002 | B1 |
| 6356282 | Roytman et al. | Mar 2002 | B2 |
| 6420968 | Hirsch | Jul 2002 | B1 |
| 6430712 | Lewis | Aug 2002 | B2 |
| 6473407 | Ditmer et al. | Oct 2002 | B1 |
| 6492901 | Ridolfo | Dec 2002 | B1 |
| 6535122 | Bristol | Mar 2003 | B1 |
| 6549135 | Singh et al. | Apr 2003 | B2 |
| 6675591 | Singh et al. | Jan 2004 | B2 |
| 6681156 | Weiss | Jan 2004 | B1 |
| 6690980 | Powell | Feb 2004 | B2 |
| 6813587 | McIntyre et al. | Nov 2004 | B2 |
| 6816811 | Seem | Nov 2004 | B2 |
| 6870141 | Damrath et al. | Mar 2005 | B2 |
| 6879253 | Thuillard | Apr 2005 | B1 |
| 6892546 | Singh et al. | May 2005 | B2 |
| 6919809 | Blunn et al. | Jul 2005 | B2 |
| 6947972 | Chun | Sep 2005 | B2 |
| 6955302 | Erdman, Jr. | Oct 2005 | B2 |
| 6973627 | Appling | Dec 2005 | B1 |
| 6990821 | Singh et al. | Jan 2006 | B2 |
| 7024283 | Bicknell | Apr 2006 | B2 |
| 7062389 | Johnson et al. | Jun 2006 | B2 |
| 7068931 | Tokunaga | Jun 2006 | B2 |
| 7069181 | Jerg et al. | Jun 2006 | B2 |
| 7085674 | Iwasawa | Aug 2006 | B2 |
| 7113085 | Havekost | Sep 2006 | B2 |
| 7171287 | Weiss | Jan 2007 | B2 |
| 7243044 | McCalla | Jul 2007 | B2 |
| 7250856 | Havekost et al. | Jul 2007 | B2 |
| 7277018 | Reyes et al. | Oct 2007 | B2 |
| 7345580 | Akamatsu et al. | Mar 2008 | B2 |
| 7457869 | Kernan | Nov 2008 | B2 |
| 7460020 | Reyes et al. | Dec 2008 | B2 |
| 7596613 | Silverthorne et al. | Sep 2009 | B2 |
| 7653459 | Pouchak et al. | Jan 2010 | B2 |
| 7819334 | Pouchak et al. | Oct 2010 | B2 |
| 20020152298 | Kikta et al. | Oct 2002 | A1 |
| 20030101009 | Seem | May 2003 | A1 |
| 20030171851 | Brickfield et al. | Sep 2003 | A1 |
| 20040143510 | Haeberle et al. | Jul 2004 | A1 |
| 20050038571 | Brickfield et al. | Feb 2005 | A1 |
| 20050043862 | Brickfield et al. | Feb 2005 | A1 |
| 20050193285 | Jeon | Sep 2005 | A1 |
| 20050203490 | Simonson | Sep 2005 | A1 |
| 20050230490 | Pouchak et al. | Oct 2005 | A1 |
| 20060136558 | Sheehan et al. | Jun 2006 | A1 |
| 20060168013 | Wilson et al. | Jul 2006 | A1 |
| 20060253205 | Gardiner | Nov 2006 | A1 |
| 20080010049 | Pouchak et al. | Jan 2008 | A1 |
| 20080015739 | Wacker | Jan 2008 | A1 |
| 20080016493 | Pouchak et al. | Jan 2008 | A1 |
| 20080115153 | Brindle | May 2008 | A1 |
| 20080125914 | Wacker | May 2008 | A1 |
| 20090113037 | Pouchak | Apr 2009 | A1 |
| 20100100583 | Pouchak | Apr 2010 | A1 |
| 20100106543 | Marti | Apr 2010 | A1 |
| 20100131653 | Dharwada et al. | May 2010 | A1 |
| 20100131877 | Dharwada et al. | May 2010 | A1 |
| 20100287130 | Guralnik et al. | Nov 2010 | A1 |
| 20110010654 | Raymond et al. | Jan 2011 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 0197146 | Dec 2001 | WO |
| WO 02052432 | Jul 2002 | WO |
| WO 03090038 | Oct 2003 | WO |
| WO 2004053772 | Jun 2004 | WO |
| WO 2004055608 | Jul 2004 | WO |
| WO 2004070999 | Aug 2004 | WO |
| WO 2005020167 | Mar 2005 | WO |
| WO 2006048397 | May 2006 | WO |
| WO 2007024622 | Mar 2007 | WO |
| WO 2007024623 | Mar 2007 | WO |
| WO 2007027685 | Mar 2007 | WO |
| WO 2007082204 | Jul 2007 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20110153033 A1 | Jun 2011 | US |