This disclosure relates generally to building control systems, and more particularly to the user interface of a building control system.
Building control systems may provide a large amount of data pertaining to HVAC equipment, security alarms, refrigeration monitoring and/or the like. In some instances, building control systems may provide such information for a large number of sites that can be within different portions of a building or within different buildings. The buildings may even be geographically scattered. Individuals charged with operating these building control systems, such as alarm managers or building superintendents, for example, may have to monitor events at multiple sites and/or diagnose and/or fix a large number of potential problems in a short amount of time.
It will be appreciated that the amount of information presented to the individual may become overwhelming. There is a need for a building control system that provides the individual with organizational tools that help manage the relatively large amounts of building control data in an efficient and intuitive manner.
This disclosure relates generally to building control systems, and more particularly to building control systems that include a user interface that is configured to help manage relatively large amounts of building control data in an efficient and intuitive manner.
In an illustrative but non-limiting example, a building control system may include a building control program that has access to building control information, and can display at least selected building control information on a display via a user interface. Sometimes through interaction with the user interface, a first set of building control information may be associated with a first display element on the display. The first display element may correspond to, for example, a window, a tab, an icon or any other suitable display element. Likewise, a second set of building control information may be associated with a second display element. The second display element may correspond to, for example, a window, a tab, an icon or any other suitable display element. In some cases, the first set of building control information may correspond to, for example, one or more building control parameters from a first geographic site or location, and the second set of building control information may correspond to one or more building control parameters from a second geographic site or location, but this is not required. The first set of building control information may be displayed when the first display element is selected for display, and the second set of building control information may be displayed when the second display element is selected for display. It is contemplated that additional sets of building control information may be associated with other corresponding display elements, as desired.
To help manage the building control information in an efficient and intuitive manner via the user interface, one or more of the first display element and the second display element may be docked in a docking display element. In some cases, the docking display element is displayed on the display when one or more of the first display element and the second display element are docked in the docking display element. The docking display element may provide a convenient way to “dock” the first display element and/or the second display element. The first display element may be docked when, for example, the user does not wish to display the first set of building control information but still wants to maintain easy access to the first set of building control information such as when subsequent monitoring of the information is anticipated or desired. Likewise, the second display element may be docked when, for example, the user does not wish to display the second set of building control information but still wants to maintain easy access to the second set of building control information. In some cases, the first display element and/or the second display element may be docked manually by the user or automatically upon the occurrence of a detected qualifying event.
The above summary is not intended to describe each and every disclosed embodiment or every implementation of the disclosure. The Description that follows more particularly exemplify the various illustrative embodiments.
The following description should be read with reference to the drawings. The drawings, which are not necessarily to scale, depict selected embodiments and are not intended to limit the scope of the disclosure. The disclosure may be more completely understood in consideration of the following detailed description of various embodiments in connection with the accompanying drawings, in which:
While the invention is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the invention to the particular illustrative embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.
The following description should be read with reference to the drawings, in which like elements in different drawings are numbered in like fashion. The drawings, which are not necessarily to scale, depict selected embodiments and are not intended to limit the scope of the invention. Although examples of construction, dimensions, and materials are illustrated for the various elements, those skilled in the art will recognize that many of the examples provided have suitable alternatives that may be utilized.
Building control system 10 may include a few or even up to thousands of building control devices. For illustrative purposes, building control system 10 is shown here with a first building control device 16, a second building control device 18 and an Nth building control device 20, where N is an integer higher than two, and may be as high as several or even many thousands. Each building control device 16, 18, 20 can be seen as being in communication with program module 12. Communication with each building control device 16, 18, 20 may be accomplished in any suitable manner. In some cases, at least some of the building control devices 16, 18, 20 may be in communication with program module 12 over a network such as a telephone network, a local area network (LAN), a wide are network (WAN) or even the Internet. In some instances, it is contemplated that at least some of the building control devices 16, 18, 20 may be in wireless communication with program module 12. The building control devices may be the same or different, and in some cases, may represent a wide variety of different devices. Illustrative but non-limiting examples include thermostats, other HVAC controllers, security alarm controllers, motion sensors, temperature sensors, pressure sensors, high temperature limit sensors and/or any other suitable device.
Building control system 10 may be configured to assist a user in viewing and/or organizing a potentially substantial amount of building control information that may be obtained from the one or more of building control devices 16, 18 and 20. For example, program module 12 may create or otherwise provide a user interface that includes graphical and/or alphanumerical display elements that may be associated with particular building control information. The display elements may be display windows, tabs, icons and the like. In some instances, program module 12 may permit the user to “dock” a display element and its associated building control information when, for example, the user does not wish to display the associate building control information, but still wants to maintain easy access to the associated building control information such as when subsequent monitoring of the information is anticipated or desired. If and/or when the user wants once again display the associated building control information, they may do so by simply selecting the appropriate display element from a docking display element.
In one example, program module 12 may associate a first set of building control information (e.g. certain building control information from a first site) with a first display element, and may associate a second set of building control information (e.g. certain building control information from a second site) with a second display element. In some cases, additional display elements may be associated with additional sets of building control information. If the first display element has been selected, such as by clicking on the first display element, the first set of building control information may be displayed on the display via display module 14. If the second display element is selected, the second set of building control information may be displayed on the display via display module 14.
It will be appreciated that reference to a first display element and a second display element is merely illustrative, as there may be tens, hundreds or even thousands of potential display elements associated with a similar number of distinct sets of building control information. Moreover, a first display element may be considered as referring to a particular display element (associated with a particular set of building control information) while a second display element may be considered as referring to a subsequent particular display element (associated with a subsequent particular set of building control information).
In some instances, display module 14 may display a docking display element. If a user desires, they can “dock” the first display element and/or the second display element in the docking display element. The docking display element may, for example, include a graphical and/or alphanumeric representation or indication of which display elements, if any, are presently docked in the docking display element. In some instances, one or more display elements assigned or associated with sets of building control information that are not being displayed or desired to be displayed may be docked in the docking display element. One or more display elements that are assigned or associated with sets of building control information that are being displayed and/or are desired to be displayed may not be docked in the docking element. In some cases, the docking display element is only displayed via display module 14 when at least one display element is currently docked, but this is not required. It is contemplated, for example, that the docking display element may be displayed at all times. In some cases, the docking display element may provide an indication of which of the one or more display elements are presently docked in the docking display element.
In some instances, the tabs may include labels other than “SITE ONE”, “SITE TWO” and so on. In some cases, the tabs may include more specific labels, referring instead, for example, to specific building control devices, two or more of which may be located at a common site. In some instances, the tabs may refer to specific HVAC equipment, to security alarms, temperature sensors and the like. It will be appreciated, therefore, that reference to “SITE ONE”, “SITE TWO” and the like is merely illustrative and is not intended to be limiting in any way.
SITE ONE tab 26 can be seen to be highlighted, indicating that it has been selected via the user interface. As a result, and in the illustrative embodiment, display window 24 displays text 34, icons, graphs, and/or any other suitable building control information that is related, assigned or otherwise associated with the SITE ONE tab 26. It will be appreciated that one may select another tab simply by clicking on or otherwise selecting the desired tab, which will cause program module 12 to display via display module 14 the appropriate information within display window 24. In some cases, one or more of the tabs may, as noted above, be docked into a docking element.
In
In some instances, one or more tabs may be docked in the docking display element 38 upon a qualifying event. For example, non-limiting examples of a qualifying event includes exceeding a number of simultaneously displayed display elements on the display. For example, a qualifying event may be triggered if the number of tabs shown in
In some instances, a user may have opened more tabs than can be displayed at one time. For example, there may be ten open tabs, while only five can be displayed at one time due to spatial limitations. In this situation, five tabs may be docked while five tabs may be open, or undocked. If the user opens another tab, say an eleventh tab, this may cause one of the currently displayed tabs to be docked. In some cases, the most recently opened tab may be docked while in other cases, it may be the first opened tab that is docked to make room for the newly opened tab. When and how particular tabs are docked or undocked may be controlled by building control system 10 (
In some cases, a qualifying event may constitute lateral movement within a hierarchal building control menu. Moving from one spot within the menu to another spot on the menu, at the same hierarchal level as the first spot, may trigger docking of one or more of the displayed display elements. In some instances, closing the docking display element may close any presently docked display elements, but this is not required.
In some instances, a display mode of a docking display element such as docking display element 38 may be changed from displaying the indication 44, 46, 48, 50, 52 of the one or more of the first display element and second display element that are docked in the docking display element 38 to not displaying the indication of the one or more of the first display element and second display element that are docked in the docking display element. In some cases, the display mode of the docking display element 38 may be set or changed based on user preferences.
In some instances, when a first display element is docked in the docking display element 38, selecting the indication (e.g. indication 44) of the first display element in the docking display element 38 selects the first display element for display and displays the first set of building control information on the display 42. In some cases, when a second display element is docked in the docking display element 38, selecting the indication (e.g. indication 46) of the second display element in the docking display element 38 selects the second display element for display and displays the second set of building control information on the display 42.
In the illustrative screen capture of
In
While
In
Docking display element 98 may include a close box 102 that, if clicked or otherwise selected, may cause building control system 10 to close any and all docked display elements. In some cases, docking display element 98 may be disposed within a particular location within display 96, while in other cases, docking display element 98 may float on the screen and thus may be moved and parked in any desired screen location by a user.
In
Control passes to block 108, where building control system 10 (
In
In some instances, as shown at block 112, one or more of the first display element and the second display element may be docked in a docking display element. In response, and at block 114, building control system 10 (
In
At block 116, an nth set of building control information, where n is an integer greater than two, may be associated with an nth display element. The nth set of building control information may pertain to information provided by an nth building control device, an nth set of building control devices, a nth building site or any other set or group of building control information. At block 118, the nth set of building control information is displayed when the nth display element has been selected. One or more of the first display element, the second display element and the nth display element may be docked in a docking display element, as seen at block 120. In some cases, the docking display element is only displayed when a display element is docked therein, but this is not required.
In
In
The disclosure should not be considered limited to the particular examples described above, but rather should be understood to cover all aspects of the invention as set out in the attached claims. Various modifications, equivalent processes, as well as numerous structures to which the invention can be applicable will be readily apparent to those of skill in the art upon review of the instant specification.
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 |
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 |
7426697 | Holecek et al. | Sep 2008 | B2 |
7457869 | Kernan | Nov 2008 | B2 |
7460020 | Reyes et al. | Dec 2008 | B2 |
7581192 | Stabb et al. | Aug 2009 | B2 |
7596613 | Silverthorne et al. | Sep 2009 | B2 |
7653459 | Pouchak et al. | Jan 2010 | B2 |
7783990 | Amadio et al. | Aug 2010 | B2 |
7819334 | Pouchak et al. | Oct 2010 | B2 |
7826929 | Wacker | Nov 2010 | B2 |
7882448 | Haug | Feb 2011 | B2 |
8000814 | Havekost et al. | Aug 2011 | B2 |
8108785 | Matthews et al. | Jan 2012 | B2 |
20020123864 | Eryurek et al. | Sep 2002 | A1 |
20030028269 | Spriggs et al. | Feb 2003 | A1 |
20030101009 | Seem | May 2003 | A1 |
20030171851 | Brickfield et al. | Sep 2003 | A1 |
20040051739 | Schmickley et al. | Mar 2004 | A1 |
20040143510 | Haeberle et al. | Jul 2004 | A1 |
20040165010 | Robertson et al. | Aug 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 |
20050283738 | Beringer et al. | Dec 2005 | A1 |
20060136558 | Sheehan et al. | Jun 2006 | A1 |
20060168013 | Wilson et al. | Jul 2006 | A1 |
20060224989 | Pettiross et al. | Oct 2006 | A1 |
20060253205 | Gardiner | Nov 2006 | A1 |
20070186175 | Hudson, Jr. | Aug 2007 | A1 |
20080010049 | Pouchak et al. | Jan 2008 | A1 |
20080016493 | Pouchak et al. | Jan 2008 | A1 |
20080115153 | Brindle | May 2008 | A1 |
20080125914 | Wacker | May 2008 | A1 |
20090062964 | Sullivan et al. | Mar 2009 | A1 |
20090077055 | Dillon et al. | Mar 2009 | A1 |
20090113037 | Pouchak | Apr 2009 | A1 |
20100100583 | Pouchak | Apr 2010 | A1 |
20100106543 | Marti | Apr 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 |
Entry |
---|
U.S. Appl. No. 12/643,865, filed Dec. 21, 2009. |
U.S. Appl. No. 12/703,476, filed Feb. 10, 2010. |
U.S. Appl. No. 12/722,364, filed Mar. 11, 2010. |
U.S. Appl. No. 12/792,547, filed Jun. 2, 2010. |
U.S. Appl. No. 12/822,997, Jun. 24, 2010. |
U.S. Appl. No. 12/977,701, filed Dec. 23, 2010. |
Honeywell Spyder Bacnet User's Guide, 242 pages, Revised Jul. 2009. |
Honeywell Spyder User's Guide 202 pages, Released Jul. 2007. |
http://blogs.msdn.com/b/khen1234/archive/2005/05/11/416392.aspx, “Regular Expressions in T-SQL,” 4 pages, May 11, 2005. |
http://en.wikipedia.org/wiki/JAR—(file—format), “JAR (file Format)—Wikipedia, the Free Encyclopedia,” 3 pages, printed Dec. 26, 2009. |
Siemens, BACnet for DESIGO 27 Pages, prior to Dec. 30, 2009. |
Tridium, “NiagaraAX Product Model Overview,” 7 pages, 2005. |
Tridium, “Tridium & Niagara Framework Overview,” 9 pages, prior to Oct. 28, 2008. |
http://www.google.com/maps, “Google Maps, Pin Location,” 1 page, prior to Nov. 21, 2008. |
Microsoft Word Screen Shots, 2 pages, prior to Nov. 21, 2008. |
Adobe Acrobat 6.0 Standard, Version 6.0.2, Screenshots, 2 pages, May 18, 2004. |
Honeywell, “Excel Building Supervisor-Integrated R7044 and FS90 Ver. 2.0,” Operator Manual, 70 pages, Apr. 1995. |
Trane, “System Programming, Tracer Summit Version 14, BMTW-SVP01D-EN,” 623 pages, 2002. |
Number | Date | Country | |
---|---|---|---|
20100131877 A1 | May 2010 | US |