HIERARCHAL SCHEDULING FOR MULTIPLE SITE BUILDING MANAGEMENT SYSTEM

One or more screens are displayed that allow a portfolio level user to create one or more portfolio level equipment schedules that are distributed from a multi-site BMS to one or more controllers at remote sites, which are configured to control operation of corresponding equipment at the remote sites in accordance with the portfolio level equipment schedules. A site level user is allowed to change a portfolio level equipment schedule and apply the changed portfolio level equipment schedule to one or more of the controllers of a remote site, resulting in an changed portfolio level equipment schedule. The portfolio level user is allowed to override the changed portfolio level equipment schedule at the first remote site and return to the portfolio level equipment schedule.

TECHNICAL FIELD

The present disclosure relates generally to building management systems, and more particularly to multi-site building management systems.

BACKGROUND

Portfolio managers may be responsible for monitoring tens, hundreds or even thousands of different building locations that may be spread out across different states or even across different nations. Each of the building locations have one or more schedules that dictate when and/or under what operating conditions (e.g. set points) various equipment operates. Maintaining multiple schedules for hundreds or even thousands of different locations, with multiple types of equipment at each location, can be daunting. What would be desirable is a multi-site management system that provides a hierarchal scheduling system that improves monitoring and control of the various building locations.

SUMMARY

The present disclosure relates generally to helping a portfolio manager create and maintain equipment schedules for a variety of different types of equipment at a number of different building locations. In an example, a method manages equipment schedules for equipment that is distributed among a plurality of remote sites that are monitored by a multi-site Building Management System (BMS). One or more screens are displayed that allow a portfolio level user to create one or more portfolio level equipment schedules. The portfolio level equipment schedules are distributed from the multi-site BMS to one or more controllers at the remote sites. The one or more controllers are configured to control operation of corresponding equipment at the remote sites in accordance with the portfolio level equipment schedules. A site level user of a first remote site is allowed to change a portfolio level equipment schedule received from the multi-site BMS and apply the changed portfolio level equipment schedule to one or more of the controllers of the first remote site, resulting in a changed portfolio level equipment schedule. Additionally or alternatively, a site level user can locally create a new schedule that overrides the portfolio level equipment schedule. The one or more controllers at the first remote site to which the changed portfolio level equipment schedule was applied are configured to control operation of corresponding equipment at the first remote site in accordance with the changed portfolio level equipment schedule. The portfolio level user is allowed to override the changed portfolio level equipment schedule at the first remote site and return to the portfolio level equipment schedule.

In another example, a method monitors adherence with an equipment schedule for equipment distributed among a plurality of remote sites. A portfolio level calendar is created at a portfolio level that provides equipment schedules. A site level calendar at each of the plurality of remote sites is originally provided as a copy of the portfolio level calendar. One or more screens are displayed that allow a portfolio level user to selectively display either the portfolio level calendar or the site level calendar corresponding to one or more of the plurality of remote sites. One or more screens are displayed that allow the portfolio level user to selectively indicate either that the portfolio level calendar is to override a site level calendar that was customized at a site level or that the site level calendar customized at the site level is to override the portfolio level calendar. Instructions are provided as to whether the equipment at the site level is to operate in accordance with the portfolio level calendar or the site level calendar.

In another example, a method creates equipment schedules for equipment that is distributed at a plurality of remote locations. One or more screens are displayed that allow a user at a supervisory level (e.g. portfolio level) to create one or more master equipment schedules. The master equipment schedules are saved in a cloud-based server. The master equipment schedules from the cloud-based server are provided to one or more controllers at one or more of the remote locations. The one or more controllers at the one or more remote locations are configured to control operation of equipment at the one or more remote locations in accordance with the master equipment schedules. In some cases, one or more of the master equipment schedules are saved at the one or more remote locations as local equipment schedules. The equipment at the one or more remote locations is operated in accordance with the local equipment schedules. Someone responsible for a remote location is allowed to customize one or more of the local equipment schedules for that remote location, resulting in one or more customized local equipment schedules. This customization may be reported to the supervisory level. Someone at the supervisory level is allowed to override one or more of the customized local equipment schedules and return to one or more non-customized local equipment schedule if desired.

DESCRIPTION

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 examples that are not intended to limit the scope of the disclosure. Although examples 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.

FIG. 1is a schematic block diagram of an illustrative system10. In its broadest terms, the illustrative system10includes a multi-site BMS12and a plurality of remote sites14. At least parts of the multi-site BMS12may be manifested on a cloud-based server, or may store data within a cloud-based server. While a total of three remote sites14are shown, it will be appreciated that this is merely illustrative, as the multi-site BMS12may oversee and/or monitor operations at a large number of remote sites14. In some cases, the multi-site BMS12may create equipment calendars at a portfolio level, and may provide these equipment calendars to each of the remote sites14. The multi-site BMS12may also monitor adherence to the equipment schedules provided by the multi-site BMS12. The remote sites14may be distributed across a large geographic area. Each of the remote sites14are individually labeled as14a,14b,14cand may each represent any of a variety of different types of sites. While each of the remote sites14may be described herein as being buildings, this is not required in all cases. For example, some of the remote sites14may also represent factories or other processing facilities.

Each of the remote sites14include a BMS16, individually labeled as16a,16b,16c. Each BMS16may be considered as being operably coupled with a number of controllers18and22. The controllers18are individually labeled as18a,18b,18cwhile the controllers22are individually labeled as22a,22b,22c. The controllers18may be considered as controlling operation of equipment20, individually labeled as20a,20b,20cwhile the controllers22may be considered as controlling operation of equipment24, individually labeled as24a,24b,24c.

It will be appreciated that there will typically be many more pieces of equipment20,24than the two that are illustrated at each remote site14. The equipment20,24may include Heating, Ventilating and Air Conditioning (HVAC) system components. The equipment20,24may include lighting system components such as indoor lighting equipment and/or outdoor lighting equipment, security system components, and the like. Each BMS16may be configured to receive operational data from the equipment20,24via the controllers18,22and to formulate control commands for the equipment20,24in response to the received operational data and in accordance with an equipment calendar. In some cases, the equipment20,24may be equipment that can be controlled in a binary fashion, i.e., the equipment20,24is either on or off.

In some cases, the BMS16may be configured to provide operational data to the multi-site BMS12. In order to communicate with the multi-site BMS12, in some cases each of the remote sites14may include a gateway26, individually labeled as26a,26b,26c. The gateways26, if present, may provide a way by which each BMS16can communicate with the multi-site BMS12. The gateways26may provide a means for operational data to be uploaded from each BMS16to the multi-site BMS12as well as control commands to be downloaded from the multi-site BMS12to each BMS16. In some cases, the gateways26may be configured to download software packages from the multi-site BMS12that better configures each BMS16for communication with the multi-site BMS12.

FIG. 2is a flow diagram showing a method of managing equipment schedules for equipment18,20that is distributed among a plurality of remote sites14that are monitored by the multi-site BMS12. One or more screens are displayed that allow a portfolio level user to create one or more portfolio level equipment schedules, as indicated at block32. In some cases, one or more of the portfolio level equipment schedules being at a time that is in the future relative to when the corresponding portfolio level equipment schedules were created. In some instances, a portfolio level user is able to create multiple schedules having differing start dates and/or differing end dates. In some cases, the portfolio level equipment schedules may, for example, include equipment ON times and equipment OFF times. In some cases, the portfolio level equipment schedules may, for example, include equipment set point schedules (e.g. comfort time period and energy saving time periods). These are just some examples. At least some of the portfolio level equipment schedules may include weekly schedules. The portfolio level equipment schedules may also include holiday schedules and/or special event schedules, for example.

In some instances, displaying one or more screens that allow the portfolio level user to create one or more portfolio level equipment schedules includes displaying a screen that includes one or more days and allows the portfolio level user to interact with the screen to create, for example, the equipment ON times and the equipment OFF times. Interacting with the screen may, for example, include grabbing an equipment ON time icon and/or an equipment OFF time icon and moving the icon on the calendar to adjust the corresponding equipment ON time and/or the equipment OFF time.

The portfolio level equipment schedules are distributed from the multi-site BMS to one or more controllers18,22at the remote sites14, as indicated at block34. The one or more controllers18,22are configured to control operation of corresponding equipment20,24at the remote sites14in accordance with the portfolio level equipment schedules, as indicated at block36. In some cases, a site level user of a first remote site14is allowed to change a portfolio level equipment schedule and apply the changed portfolio level equipment schedule to one or more of the controllers18,22of the first remote site14, resulting in an changed portfolio level equipment schedule, as indicated at block38. The one or more controllers18,22at the first remote site14to which the changed portfolio level equipment schedule was applied control operation of corresponding equipment20,24at the first remote site14in accordance with the changed portfolio level equipment schedule, as indicated at block40. The portfolio level user is allowed to override the changed portfolio level equipment schedule at the first remote site14and return to the portfolio level equipment schedule, as indicated at block42. In some cases, and as optionally indicated at block44, an identifier may be provided on one or more screens of the multi-site BMS12that identifies to the portfolio level user that the site level user has changed the portfolio level equipment schedule.

FIG. 3is a flow diagram showing an illustrative method50of monitoring adherence with an equipment schedule for equipment distributed among a plurality of remote sites14. A portfolio level calendar is created at a portfolio level that provides equipment schedules, and there is a site level calendar at each of the plurality of remote sites, the site level calendar at each of the plurality of remote sites14originally provided as a copy of the portfolio level calendar for that equipment. The portfolio level calendar may, for example, include scheduling information for local equipment that relies upon binary control or set point control. In some instances, the portfolio level calendar may include scheduling information for lighting equipment, HVAC equipment, security equipment and/or any other suitable building control equipment.

As indicated at block52, one or more screens are displayed that allow a portfolio level user to selectively display the portfolio level calendar, as indicated at block54or the site level calendar corresponding to one or more of the plurality of remote sites, as indicated at block56. As indicated at block58, one or more screens are displayed that allow the portfolio level user to selectively indicate that the portfolio level calendar is to override a site level calendar that was customized at a site level, as indicated at block60, or to indicate that the site level calendar customized at the site level is to override the portfolio level calendar, as indicated at block62. Instructions are provided as to whether the equipment20,24at the site level is to operate in accordance with the portfolio level calendar or the site level calendar, as indicated at block64.

In some cases, and as optionally indicated at block66, one or more screens may be displayed that display a list of all equipment schedules of site level calendars that differ from the equipment schedule represented by the portfolio level calendar. In some instances, and as optionally indicated at block68, one or more screens may be displayed that display a list of all remote sites14of the plurality of remote sites14that failed to update when a revised portfolio level calendar including a revised equipment schedule is created at the portfolio level and downloaded to the remote sites. One or more screens may be displayed that list all of the equipment at the remote sites that is operating in accordance with a site level calendar that was customized at the site level, as optionally indicated at block70.

FIG. 4is a flow diagram showing an illustrative method80of creating equipment schedules for equipment20,24that is distributed at a plurality of remote locations. One or more screens are displayed that allow a user at a supervisory level to create one or more master equipment schedules, as indicated at block82. The master equipment schedules are saved in a cloud-based server, as indicated at block84. The master equipment schedules from the cloud-based server are provided to one or more controllers18,22at one or more of the remote locations, the one or more controllers18,22at the one or more remote locations configured to control operation of equipment20,24at the one or more remote locations in accordance with the master equipment schedules, as indicated at block86. The one or more of the master equipment schedules are saved at the one or more remote locations as local equipment schedules, as indicated at block88.

The equipment20,24at the one or more remote locations is operated in accordance with the local equipment schedules, as indicated at block90. Someone responsible for a remote location is allowed to customize one or more of the local equipment schedules for that remote location, resulting in one or more customized local equipment schedules, as indicated at block92. Someone at the supervisory level is allowed to override one or more of the customized local equipment schedules and return to one or more non-customized local equipment schedule, as indicated at block94. In some cases, and as optionally indicated at block96, a screen may be displayed that identifies to a user at the supervisory level the customized local equipment schedules at each of two or more of the remote locations.

FIGS. 5 through 27show illustrative screens of a multi-site BMS for creating and monitoring equipment schedules.FIG. 5shows a screen100that illustrates how an organization hierarchy might translate into a calendar that provides an equipment schedule. The screen100includes a first panel102that shows geographic regions such as North Region, South Region, West Region and East Region for a company named ABC Retail Clothing Store. A second panel104shows what might be displayed if someone selects the South Region in the first panel102. The second panel104shows individual locations within the South Region, such as Alabama, Ashford, Santiago and San Paulo. The screen100includes a third panel106that shows what might be displayed if someone selects Ashford in the second panel104. The third panel106displays options such as indoor lighting sections, indoor VRF (variable refrigerant flow units), parking lights and signage lights. The screen100includes a banner108that shows this hierarchical relationship in a bread crumb format, starting with the portfolio level.

FIG. 6shows a screen110that illustrates a list view of a portfolio-level equipment schedule. The screen110includes a list of schedule names112, a list of effective dates114, a list of who created the schedules116and a list of how the schedules were applied118. It will be appreciated that the screen110includes a Create Schedule button120that may be used to create a new equipment schedule, for example.

FIG. 7shows a screen122that once again includes a Create Schedule button120, but also includes a Set Holidays button124. The screen122provides an example of a portfolio-level calendar view of an equipment schedule. In the example given, the screen122shows a weekly portfolio lighting schedule for ABC Retail Clothing Stores. In this equipment schedule, lighting is scheduled to be on every day Monday through Sunday, from 9 am (shown as 0900 hours) to 8 pm (shown as 2000 hours). It will be appreciated that only a portion of the screen122is visible. One may scroll vertically to see the rest of the calendar.

FIG. 8shows a screen130that includes both the Create Schedule button120and the Set Holidays button124. The screen130shows a weekly portfolio-level calendar schedule (same as shown inFIG. 7), but the screen130includes an icon132on each day of the week that indicates that the South Region is running in accordance with the portfolio-level calendar schedule that was received by the South Region. The screen130includes an indicator134showing that the displayed calendar pertains to the South Region.

FIG. 9shows a screen140that includes both the Create Schedule button120and the Set Holidays button124. The screen140shows a weekly portfolio-level calendar schedule (same as shown inFIG. 7), but the screen140includes an icon132on each day of the week that indicates that the Ashford location is running in accordance with the portfolio-level calendar schedule that was received by the Ashford. The screen140includes an indicator144showing that the displayed calendar pertains to the Ashford location.

FIG. 10shows a screen150that includes both the Create Schedule button120and the Set Holidays button124. As evidenced by the indicator134, the screen150pertains to the South Region but includes multiple schedules. As can be seen, the screen150shows a portfolio-level indoor lighting schedule152that runs Monday through Sunday and specifies operation of the indoor lighting every day from 3 pm (1300 hours) to 8 pm (2000 hours). The screen150also shows a portfolio-level RTU (roof top unit) schedule154that runs Monday through Friday from 9 am (0900 hours) to 6 pm (1800 hours) and runs Saturday through Sunday from 11 am (1100 hours) to 5 pm (1700 hours). The screen150also shows a portfolio-level outdoor lighting schedule156that runs Monday through Sunday from 6 pm (1800 hours) to 11 pm (2300 hours). Each of the schedules152,154and156can be seen to include the icon132that indicates that the South Region is operating in accordance with each of the portfolio-level schedules.

FIG. 11shows a screen160that includes a child calendar created locally for the Ashford location, as seen by the indicator144. The screen160includes a message162saying that the schedule was successfully created and deployed at the Ashford location. The screen160shows a local indoor lighting schedule that replaces the portfolio-level indoor lighting schedule. The new customized indoor lighting schedule for the Ashford location runs Monday through Friday from 9 am (0900 hours) to 6 pm (1800 hours) and runs Saturday through Sunday from 8 am (0800 hours) to 11 pm (2300 hours). The icon132is not shown on this customized schedule, which is a visual queue to the portfolio level user that the schedule is not the portfolio-level calendar schedule.

FIG. 12shows a screen170that may be used to create a schedule calendar. The screen170includes a details panel172that includes various details for the calendar as well as a calendar panel174in which a user can set the equipment On and equipment OFF times for whatever equipment schedule is being created. As seen in the details panel172, the schedule being created is an indoor lighting schedule to be used by several locations in the South Region. As seen in the calendar panel174, the schedule being created runs Monday through Friday from 9 am (0900 hours) to 6:30 pm (1830 hours) and runs Saturday through Sunday from 8 am (0800 hours) to 8:30 pm (2030 hours). The screen170includes a Create button176that can be used to save and implement the proposed schedule as shown in the calendar panel174.

FIG. 13shows a screen180that may be used to create a schedule calendar. The screen180includes a details panel182that shows the different types of calendars that can be created. As seen in the details panel182, a user can create a special event calendar, a holiday calendar or a weekly calendar. In some cases, a different color or pattern may be used as the calendar marker that shows the daily equipment start and stop times. As an illustrative but non-limiting example, the calendar markers may be purple for a weekly calendar, orange for a holiday calendar and blue for a special calendar. It will be appreciated that a myriad of other colors and/or patterns may be used to indicate the type of calendar being displayed.

FIG. 14shows a screen190that may be used to create a schedule calendar. The screen190includes a details panel192that shows all of the supported types of equipment. It is contemplated, of course, that additional types of equipment may be supported as well. As seen in the details panel192, supported types of equipment may include lighting, RTU (roof top units), exhaust fans and refrigerators. Additional types of supported equipment may be specified by scrolling down if appropriate.

FIG. 15shows a screen200that may be used to create a schedule calendar. The screen200includes a details panel202and a calendar panel204. The details panel202includes a listing of all the possible groups of equipment. In the given example, the details panel202shows the different groups of lighting. It will be appreciated that the groups of equipment that are shown will depend on what is selected in the screen190(FIG. 14). In some cases, these groups may be user-configurable. As seen in the calendar panel204, the person creating the schedule may not be done, as they are creating a weekly schedule but only have one day filled in thus far.

FIG. 16shows a screen210that may be used to create a special events calendar. The screen210includes a details panel212, an events panel214and a recurrence panel216. As seen in the details panel212, a special event indoor lighting calendar is being created. As seen in the events panel214, the lighting will be on from 9 am (0900 hours) to 6:30 pm (1830 hours). As seen in the recurrence panel216, this special event will occur on the second Saturday of the month.FIG. 17provides a screen220that is similar to the screen210, but provides other options within the recurrence panel216. In this case, the special event is designated as a one-time event, and thus does not repeat.

FIG. 18shows a screen230that may be used to create a holiday calendar. The screen230includes a Basic Details panel232, a Holiday Events panel234and a Holiday List panel236. The Basic Details panel232provides information regarding the name of the schedule, what type of calendar it is and what level it will be applied at. In the example given, a global holiday weekly calendar at the portfolio level is being created. The Holiday Events panel234shows the type of equipment that will be included while the Holiday List panel236includes a list of possible holidays and their usual duration. The user is able to select a holiday from the list or is able to delete a holiday from the list. The user is also able to create a new holiday. The screen230includes a Save and Create button238.

FIG. 19shows a screen240that provides a calendar view, rather than a list view, for creating holiday schedules. The screen240includes a panel242that shows a legend for the holiday schedules being displayed within a calendar panel244. As indicated in the legend, the screen240includes global holidays, North Region holidays, South Region holidays and East Region holidays. The screen240includes a Create Holiday List button246, which may be used to revert to the screen230, for example.

FIG. 20shows a screen250that illustrates how a calendar may be created and then copied to create additional schedules. The screen250includes a parent schedule portion252and a child schedule portion254. The parent schedule portion252shows a weekly indoor lighting schedule for Ashford, which is being copied over to, as indicated by the child schedule portion254, Alabama and Santiago (several other locations in the South Region). The screen250includes a Select button252.

FIG. 21shows a screen260that provides a schedule summary that allows a user to track the status of particular schedules by its children calendars. For a specific schedule, a complete report may be generated that includes a (1) list of all of the child calendars that were supposed to inherit this schedule but are instead following a local schedule, (2) a list of all controllers or gateways that failed to download, and (3) a list of all equipment that is running on manual override (e.g. no schedule). The screen260includes a site schedule summary262that provides an icon266that is a total number of sites as well as totals for each of (1), (2) and (3) under an icon268, an icon270and an icon272, respectively. The screen260also includes a list264that shows all of the sites, as evidenced by the icon266being highlighted (e.g. underlined).

FIG. 22shows a screen280that is similar to the screen260shown inFIG. 21, but instead provides a listing of schedule exceptions. It can be seen that the icon268, for Schedule Exceptions, is highlighted (e.g. underlined). The screen280includes a list282of schedule exceptions and a panel284that graphically illustrates each of the schedule exceptions. Several actions can be taken. One option is a Resolve Exception, which involves overwriting the child calendars with the schedules on parent calendars (e.g. portfolio level equipment schedules) against which the child calendars (e.g. local equipment schedules) are being compared. For gateways and controllers for which a download failed, the user can retry the download. In some cases, a supervisor may decide to dynamically turn off a manual override and instead revert operation to a regular schedule.FIG. 23shows a screen290that may be used in resolving schedule conflicts.

FIG. 24provides a screen300that shows a schedule for the Ashford location, as seen by the indicator144. The screen300includes a schedule panel302that graphically illustrates the schedule, as well as a details panel304that provides a quick summary regarding exceptions, download failures and the like.FIG. 25shows a screen310that includes the schedule panel302and an activity log312.

FIG. 26provides a screen320that shows a schedule for the Ashford region that includes all types of schedules. As shown, the screen320includes a weekly schedule322, a holiday schedule324and a special events schedule326.FIG. 27provides a screen330that provides a monthly view of all schedules at a portfolio level, as seen by an indicator332. Any of the schedules shown can be clicked on to obtain additional detail.

Having thus described several illustrative embodiments of the present disclosure, those of skill in the art will readily appreciate that yet other embodiments may be made and used within the scope of the claims hereto attached. It will be understood, however, that this disclosure is, in many respects, only illustrative. Changes may be made in details, particularly in matters of shape, size, arrangement of parts, and exclusion and order of steps, without exceeding the scope of the disclosure. The disclosure's scope is, of course, defined in the language in which the appended claims are expressed.