Patent Application
20160179069
The present disclosure relates to devices, methods, and systems for controlling a building management system.
Building information modeling (BIM) can refer to the generation and/or management of data associated with a building (e.g., data associated with the components, equipment, and/or properties of the building). For example, BIM data can include architectural, mechanical, electrical, plumbing, sanitary, fire, and/or geometrical information associated with a building.
BIM data associated with a building can be used to generate a user interface for a building management system for the building, which can be displayed to a user (e.g., operator) and used to monitor and/or control the building. For example, the user (e.g., operator) of a building management system can check and/or set the state of a control component(s), equipment, device(s), network (s) area(s), and/or space(s) of the building using the user interface of the building management system.
Devices, methods, and systems for controlling a building management system (BMS) are described herein. For example, one or more embodiments can include authenticating a user for access to a number (e.g., a plurality) of building management system applications. The authentication can include determining an identity of the user, determining access rights of the user, and determining a location of the user. One or more embodiments can include receiving information from the user associated with at least one of the number of applications.
Embodiments of the present disclosure can decrease the amount of time and/or computing resources needed to be authenticated for each user to access a BMS system. For example, a number (e.g., a plurality) of applications of a BMS system can be accessed by a user at a single location with a single authentication procedure. Further, the number of applications can be used by the user to control a number of aspects of the BMS system.
In the following detailed description, reference is made to the accompanying drawings that form a part hereof. The drawings show by way of illustration how one or more embodiments of the disclosure may be practiced.
These embodiments are described in sufficient detail to enable those of ordinary skill in the art to practice one or more embodiments of this disclosure. It is to be understood that other embodiments may be utilized and that process, electrical, and/or structural changes may be made without departing from the scope of the present disclosure.
The figures herein follow a numbering convention in which the first digit or digits correspond to the drawing figure number and the remaining digits identify an element or component in the drawing. Similar elements or components between different figures may be identified by the use of similar digits. For example, 102 may reference element “02” in
As will be appreciated, elements shown in the various embodiments herein can be added, exchanged, combined, and/or eliminated so as to provide a number of additional embodiments of the present disclosure. The proportion and the relative scale of the elements provided in the figures are intended to illustrate the embodiments of the present disclosure, and should not be taken in a limiting sense.
As used herein, “a” or “a number of” something can refer to one or more such things. For example, “a number of buildings” can refer to one or more buildings.
As shown in
A number of devices (e.g., device 102) can be connected to and/or in communication with a mobile backend service 108. The mobile backend service 108 can be scalable (e.g., flexible, changeable, dynamic, etc.) and change based on a changing parameter within the BMS system. A BMS building parameter can include at least one of a building access parameter (e.g., level of access rights to the building), a building security parameter (e.g., level of security of a building), a building environment parameter (e.g., related to temperature, pressure, air flow, etc.), a building operations parameter (e.g., operations of the building), and a building safety parameter (e.g., safety regulations and safety measures used by the building).
The mobile backend service 108 can be in communication with an Application Program Interface (API), such as BMS API 106, as illustrated in
As used herein, a “network” can provide a communication system that directly or indirectly links two or more computers and/or peripheral devices and allows users to access resources on other computing devices and exchange messages with other users. A network can allow users to share resources on their own systems with other network users and to access information on centrally located systems or on systems that are located at remote locations. For example, a network can tie a number of computing devices together to form a distributed control network.
A network may provide connections to the Internet and/or to the networks of other entities (e.g., organizations, institutions, etc.). Users may interact with network-enabled software applications to make a network request, such as to get a file or print on a network printer. Applications may also communicate with network management software, which can interact with network hardware to transmit information between devices on the network.
A user of the device 102 can interact with a server (e.g., a BMS Front End Server) 110 through the BMS API 106. The BMS API 106 can provide (e.g., for display and/or presenting) to the user of the device 102. For instance, in some embodiments, the BMS API 106 can provide graphical user interface (GUI) information that can include information to be displayed (e.g., on a screen) provided to and/or received from the user of the device 102. The information can be displayed, for instance, on a touch-screen (e.g., the GUI can include touch-screen capabilities through a GUI on the device 102). Embodiments of the present disclosure, however, are not limited to a particular type(s) of user interface.
The BMS API 106 can allow a number of users to access a number of applications (e.g., applications 224-1 and 224-2 described in connection with
The building data can be gathered from a number (e.g., a plurality) of users to determine a larger preference (e.g., poll the number of users). For example, a request can be sent to the number of users to indicate whether each of the number of users are hot or cold, warm or cool, etc. A preference of temperature can be requested from each of the number of users. The determination of whether to increase or decrease the temperature of the location can be determined based on data received from the number of users pertaining to their preference. A request can be sent to indicate a particular temperature for the location and an average temperature, mean temperature, median temperature, or a number of group-based temperature outcomes can be determined and the temperature can be changed to one of these temperatures.
The building data can be gathered from a number (e.g., a plurality) of users to indicate whether each of the users are “safe” and/or “in danger.” For example, during or immediately following a particular event (e.g., an earthquake, a fire, a natural disaster, an unsafe incident, etc.) a request can be sent to each of the number of users to indicate whether the number of users are safe and/or in danger in relation to that event. A number of indications can be provided for a response. For example, indications can include safe, protected, in a safe location, evacuated, still inside but safe, still inside and in danger, etc. The group data (e.g., social data) can be returned by the number of users to the Front End Server 110 and the group data can be analyzed and/or used to determine how to change a particular building parameter.
As shown in
Memory 114 can be volatile or nonvolatile memory. Memory 114 can also be removable (e.g., portable) memory, or non-removable (e.g., internal) memory. For example, memory 114 can be random access memory (RAM) (e.g., dynamic random access memory (DRAM) and/or phase change random access memory (PCRAM)), read-only memory (ROM) (e.g., electrically erasable programmable read-only memory (EEPROM) and/or compact-disk read-only memory (CD-ROM)), flash memory, a laser disk, a digital versatile disk (DVD) or other optical disk storage, and/or a magnetic medium such as magnetic cassettes, tapes, or disks, among other types of memory.
Further, although memory 114 is illustrated as being located in the BMS Front End Server 110, embodiments of the present disclosure are not so limited. For example, memory 114 can also be located internal to another computing resource (e.g., enabling computer readable instructions to be downloaded over the Internet or another wired or wireless connection).
The BMS Front End Server 110 can be in communication with a number of BMS systems. The number of BMS systems can include, for example, a security system 104-1, a safety system 104-2, an energy system 104-3, and a Heating/Ventilation/Air Conditioning (HVAC) system 104-4. The number of BMS systems can be associated with at least one of tenants, visitors, safety, energy, environment, building operations, and facility management. However, the number of BMS systems are not limited to those listed and are provided as examples.
The security system 104-1 can control security related issues for a building of the BMS. For example, information from a user of device 102 can provide security information so that the BMS can verify the user's identity and allow the user to access the building.
The safety system 104-2 can control safety related issues for the building of the BMS. For example, BMS information from at least one of the BMS system and/or the user can control safety measures such as air purification, smoke monitoring, temperature monitoring, etc. to insure the building is safe.
The energy system 104-3 can control energy related issues for the building. For example, energy usage by a number of users (e.g., a user of device 102) can be managed and/or monitored based on energy information received from the number of users.
The HVAC system 104-4 can control HVAC related issues for the building of the BMS. For example, a user's preference (e.g., a user of device 102) can determine heating and/or cooling of a particular room that the user is going to enter or is already occupying.
Device 202 can include a number of applications 224-1, 224-2. The number of applications 224-1, 224-2 can be associated with at least one of room comfort control, mobile access control, visitor management, location based services, and facility management. While the list of possible applications is provided as an example, applications in embodiments are not so limited.
A user of device 202 can interact with the number of applications 224-1, 224-2 to send a request to the BMS system and/or to provide BMS information. For example, the user can use an application (e.g., one of applications 224-1) to request a change in a temperature of a room (e.g., related to room comfort control). That is, the user can make a selection on a room control application of the number of applications on the device 202 and the BMS system can adjust a control of the room associated with the location of the user. The user can use an application to request mobile access to the BMS system (e.g., related to mobile access control). The user can use an application to manage a visit to the building location (e.g., related to visitor management). The user can use an application to request information about a location of the building and/or a location of the user (e.g., location based services). The user can use an application to provide building information about the building facility to the BMS system (e.g., related to facility management).
In order to communicate with the BMS system, a user of the device 202 can use an application container 226 to enter user information through an API 228 in communication with the BMS system (e.g., mobile backend service 108 in
For example, a user can have physical access rights to a portion of the building that the user is performing maintenance on, monitoring, etc. A user that is visiting the building can have access rights related to visitor locations in the building. A user can have access rights to a subset of the building. A user can have access rights to use a subset of the applications on the device 102 to control parameters of the building based on the user's access rights and/or which facility the user is located within.
The user can indicate a selection on an application of a number of applications on the device 202 associated with building access. The selection can indicate a request to enter an additional location of the building. The selection can be made by the user using a GUI to interact with the API 228 to send selection information to the BMS front end server 110. When a user is requesting physical access, a virtual key can be sent to the user of the device 202 the made the selection. The virtual key can provide physical access to the additional location for the user using the virtual key.
A mobile backend service (e.g., mobile backend service 108 in
The application exchange can manage the number of BMS applications by monitoring logins of a number of users. The application exchange can allow access to all of the number of applications for a single login to the application exchange made by each of the logins of the number of users the application exchange is monitoring and/or receiving information from.
The method can include, at block 332, authenticating a user for access to a number of building management system (BMS) applications. The authentication can include, at block 334-1, determining an identity of the user. For example, a username and/or password can be used to verify a user's identity.
The authentication can include, at block 334-2, determining access rights of the user. For example, based on how the user is associated with the BMS, the user can be given particular access rights. A user that works at the building can have more access rights than a visitor to the building.
The authentication can include, at block 334-3, determining a location of the user. For example, authenticating a user to enter a particular location can be based on where the user is in relation to the building. In some embodiments, the access rights of the user can change based on the location of the user. For example, an employee can have different access rights based on which building location the employee is at. The employee may work at a first building location and have more access rights and visit a second building location where the employee has fewer access rights.
The method 330 can include, at block 336, receiving information from the user associated with at least one of a number of applications. The received information can include information associated with a number of parameters of the BMS system. The user can be tasked with entering the parameter information at a particular number of intervals of time. The user can enter parameter information based on parameter changes. The user can enter parameter information requesting to change the parameter. The received information can be gathered from a number of users and aggregated to make decisions based on a plurality of data points. The received information can be used for record keeping and further analysis at a later time.
The BMS applications associated with the BMS can be associated with a number of systems of the BMS. At least one application of the BMS applications can be associated with at least one of a security system, a safety system, an energy system, and a Heating Ventilation and Air Conditioning (HVAC) system. The at least one application of the number of BMS applications can be associated with at least one of a room comfort control, a mobile access control, a visitor management, a location based service, and facility management. The at least one application can be associated with location based services and can send a map of a layout of a building to the user to navigate the building.
Although specific embodiments have been illustrated and described herein, those of ordinary skill in the art will appreciate that any arrangement calculated to achieve the same techniques can be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments of the disclosure.
It is to be understood that the above description has been made in an illustrative fashion, and not a restrictive one. Combination of the above embodiments, and other embodiments not specifically described herein will be apparent to those of skill in the art upon reviewing the above description.
The scope of the various embodiments of the disclosure includes any other applications in which the above structures and methods are used. Therefore, the scope of various embodiments of the disclosure should be determined with reference to the appended claims, along with the full range of equivalents to which such claims are entitled.
In the foregoing Detailed Description, various features are grouped together in example embodiments illustrated in the figures for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the embodiments of the disclosure require more features than are expressly recited in each claim.
Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.
This application is a Non-Provisional of U.S. Provisional Application No. 62/093,531, filed Dec. 18, 2014, the contents of which are incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 62093531 | Dec 2014 | US |
