Patent Application
20230161306
The present disclosure relates generally to a user interface for viewing information relating to a building management system (BMS). A BMS is, in general, a system of devices configured to control, monitor, and manage equipment in or around a building or building area. A BMS can include, for example, a heating, ventilation, and air conditioning (HVAC) system, a security system, a lighting system, a fire alerting system, any other system that is capable of managing building functions or devices, or any combination thereof.
Information about the BMS is typically accessed via a user interface generated by the BMS. A user may access the user interface via a user device such as a desktop, laptop, tablet, or mobile device. The user may generally access information about one or more spaces within the BMS, or one or more equipment within the BMS. For example, a user may view the current status of an area (e.g., occupancy, temperature, etc.), the current status of equipment (e.g., if equipment requires maintenance or replacement, if the equipment is malfunctioning), or any alarms or warning relating to the building or BMS.
Individual components within the BMS may have a wide-ranging impact on other components and various spaces in the BMS. For example, a change in the operation of a piece of equipment may impact multiple spaces and multiple BMS systems (e.g., an adjustment of a control strategy of an air handling unit of a HVAC system may negatively impact the performance of the HVAC system, causing additional energy to be used or a setpoint to not be reached). When such a change or other issue occurs in a BMS with a particular piece of equipment, space, or system, it may be difficult to diagnose the change or issue. Accordingly, it would be desirable to have systems and methods for generating a user interface that can provide users with information about how the operation of the various components of a BMS affect each other.
One implementation of the present disclosure relates to a building system for a building having one or more building subsystems. The building system includes one or more memory devices. The one or more memory devices have instructions stored thereon that, when executed by one or more processors, cause the one or more processors to acquire a selection of a first object where the first object represents a component of the one or more building subsystems, acquire information regarding one or more second objects associated with the first object where the information includes an involvement type for a relationship between the first object and each of the one or more second objects, and generate an involvement map for display via a graphical user interface. The involvement map includes a first indicia representing the first object and one or more second indicia representing each of the one or more second objects. The first indicia and each of the one or more second indicia are connected via a connector line. The connector line includes the involvement type disposed therealong.
Another implementation of the present disclosure relates to a method for providing a graphical user interface that displays involvement between components of one or more building subsystems. The method includes acquiring, by one or more processing circuits, a selection of a first object where the first object represents a component of the one or more building subsystems; acquiring, by the one or more processing circuits, information regarding one or more second objects associated with the first object here the information includes an involvement type for a relationship between the first object and each of the one or more second objects; and generating, by the one or more processing circuits, an involvement map for display via the graphical user interface. The involvement map includes a first indicia representing the first object and one or more second indicia representing each of the one or more second objects. The first indicia and each of the one or more second indicia are connected via a respective connector line. The respective connector line includes the involvement type disposed therealong. The involvement type indicates whether the relationship between the first object represented by the first indicia and a respective second object of the one or more second objects represented by a respective one of the one or more second indicia is a referential involvement, a command involvement, or an unbound involvement.
Still another implementation of the present disclosure relates to a building system for a building having one or more building subsystems. The building system includes one or more memory devices. The one or more memory devices have instructions stored thereon that, when executed by one or more processors, cause the one or more processors to acquire a selection of a first object where the first object represents a component of the one or more building subsystems, acquire the information regarding one or more second objects and one or more third objects associated with the first object where (i) the information includes an involvement type for a relationship between (a) the first object and each of the one or more second objects and (b) the first object and each of the one or more third objects, (ii) the one or more second objects have an upstream involvement with the first object, and (iii) the one or more third objects have a downstream involvement with the first object, and generate an involvement map for display via a graphical user interface. The involvement map includes a first indicia representing the first object, one or more second indicia representing each of the one or more second objects, and one or more third indicia representing each of the one or more third objects. (a) The first indicia and each of the one or more second indicia and (b) the first indicia and the each of the one or more third indicia are connected via a respective connector line. The respective connector line includes the involvement type disposed therealong. The involvement type indicates whether the relationship between (a) the first object represented by the first indicia and (b) a respective second object of the one or more second objects represented by a respective one of the one or more second indicia or a respective third object of the one or more third objects represented by a respective one of the one or more third indicia is a referential involvement, a command involvement, or an unbound involvement.
Referring generally to the figures, systems and methods for providing a user interface for monitoring and controlling multiple components in a BMS are shown, according to exemplary embodiments. More particularly, the user interface described herein is configured to provide information about the relationship between various components in the BMS and the control logic associated with the components.
In a BMS, a supervisory level controller may generally implement supervisory level control for the various components of a BMS. The supervisory level controller may, for example, provide a general control strategy for multiple components of a BMS, without providing instructions for individual controllers for an individual component or piece of equipment. The relationship between the supervisory level control and the control of individual components or objects in a BMS may generally be inaccessible or not understandable due to the complexity of the BMS.
In some embodiments, a user may access such information via a user interface. For example, on the user interface, the user may select an object representing a component in the BMS (e.g., a piece of equipment, a building area, a subsystem, etc.). The object may include references to other objects in the BMS related to the object. The user may run a report that shows the relationship between the object and other objects. However, it may be difficult for a user to see how the high level control from the supervisory controller affects the object.
The user interface described herein may be configured to provide an interactive view that can be used to understand what is affecting an object in the BMS. The user interface may be used to identify software objects, user actions, and high-level control logic what affect the object. Further, the user interface may identify a control sequence and allow a user to traverse the control sequence at any level in the control “chain.” In other words, the user may view how control logic impacts each individual object in the BMS impacted by the control logic. This allows the user to more clearly understand why a particular condition is occurring for an object in a BMS in response to the implementation of control logic.
In some implementations, the user interface provides an interactive view at an equipment level, allowing the user to see the impact of control logic for a piece of equipment and all other related pieces of equipment (i.e., all equipment impacted by the specific piece of equipment). In other implementations, the user interface provides an interactive view at a space level, allowing the user to see the impact of control logic for all components in a particular space.
At any level in the control sequence, the user interface may be configured to provide an indication of any user change that affects the object, equipment, or space represented at the level in the control sequence shown. This allows the user to gain a better understanding of how a user change affects a specific piece of equipment, or how a user change affects the overall control strategy in the BMS.
Referring now to
BMS controller 101 can include one or more computer systems (e.g., servers, supervisory controllers, subsystem controllers, etc.) that serve as system level controllers, application or data servers, head nodes, or master controllers for serving a building or building area. BMS controller 101 can communicate with multiple downstream building systems or subsystems (e.g., a HVAC system, a security system, a lighting system, etc.) via a communications link according to like or disparate protocols (e.g., LON, BACnet, etc.).
BMS 100 can be implemented in a building to automatically monitor and control various building functions. BMS 100 is shown to include a BMS controller 101 and a plurality of building subsystems 128. Building subsystems 128 are shown to include a fire safety subsystem 130, a lift/escalators subsystem 132, a building electrical subsystem 134, an information communication technology (ICT) subsystem 136, a security subsystem 138, a HVAC subsystem 140, and a lighting subsystem 142. In various embodiments, building subsystems 128 can include fewer, additional, or alternative subsystems. For example, building subsystems 128 can also or alternatively include a refrigeration subsystem, an advertising or signage subsystem, a cooking subsystem, a vending subsystem, a printer or copy service subsystem, or any other type of building subsystem that uses controllable equipment and/or sensors to monitor or control a building. In some embodiments, building subsystems 128 and more particularly HVAC subsystem 140 can include a waterside system and/or an airside system.
Each of building subsystems 128 can include any number of devices, controllers, and connections for completing its individual functions and control activities. HVAC subsystem 140 can include, for example, a chiller, a boiler, any number of air handling units, economizers, field controllers, supervisory controllers, actuators, temperature sensors, and other devices for controlling the temperature, humidity, airflow, or other variable conditions within a building. Lighting subsystem 142 can include any number of light fixtures, ballasts, lighting sensors, dimmers, or other devices configured to controllably adjust the amount of light provided to a building space. Security subsystem 138 can include occupancy sensors, video surveillance cameras, digital video recorders, video processing servers, intrusion detection devices, access control devices (e.g., card access, etc.) and servers, or other security-related devices.
BMS controller 101 is shown to include a communications interface 107 and a BMS interface 109. Communications interface 107 can facilitate communications between BMS controller 101 and external applications (e.g., monitoring and reporting applications 122, enterprise control applications 126, remote systems and applications 144, applications residing on client devices 148, etc.) for allowing user control, monitoring, and adjustment to BMS controller 101 and/or subsystems 128. Communications interface 107 can also facilitate communications between BMS controller 101 and client devices 148. BMS interface 109 can facilitate communications between BMS controller 101 and building subsystems 128 (e.g., HVAC, lighting security, lifts, power distribution, business, etc.).
Interfaces 107, 109 can be or include wired or wireless communications interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc.) for conducting data communications with building subsystems 128 or other external systems or devices. In various embodiments, communications via interfaces 107, 109 can be direct (e.g., locally wired or wireless communications) or via a communications network 146 (e.g., a WAN, the Internet, a cellular network, etc.). For example, interfaces 107, 109 can include an Ethernet card and port for sending and receiving data via an Ethernet-based communications link or network. In another example, the interfaces 107, 109 can include a Wi-Fi transceiver for communicating via a wireless communications network. In another example, one or both of interfaces 107, 109 can include cellular or mobile phone communications transceivers. In one embodiment, communications interface 107 is a power line communications interface and BMS interface 109 is an Ethernet interface. In other embodiments, communications interface 107 and BMS interface 109 are Ethernet interfaces or are the same Ethernet interface.
BMS controller 101 is shown to include a processing circuit 104 including a processor 106 and memory 108. Processing circuit 104 can be communicably connected to BMS interface 109 and/or communications interface 107 such that processing circuit 104 and the various components thereof can send and receive data via interfaces 107, 109. Processor 106 can be implemented as a general purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable electronic processing components.
Memory 108 (e.g., memory, memory unit, storage device, etc.) can include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing data and/or computer code for completing or facilitating the various processes, layers and modules described in the present application. Memory 108 can be or include volatile memory or non-volatile memory. Memory 108 can include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present application. According to an exemplary embodiment, memory 108 is communicably connected to processor 106 via processing circuit 104 and includes computer code for executing (e.g., by processing circuit 104 and/or processor 106) one or more processes described herein.
In some embodiments, BMS controller 101 is implemented within a single computer (e.g., one server, one housing, etc.). In various other embodiments BMS controller 101 can be distributed across multiple servers or computers (e.g., that can exist in distributed locations). Further, while
Memory 108 is shown to include an enterprise integration layer 110, an automated measurement and validation (AM&V) layer 112, a demand response (DR) layer 114, a fault detection and diagnostics (FDD) layer 116, an integrated control layer 118, and a building subsystem integration later 120. Layers 110-120 can be configured to receive inputs from building subsystems 128 and other data sources, determine optimal control actions for building subsystems 128 based on the inputs, generate control signals based on the optimal control actions, and provide the generated control signals to building subsystems 128. The following paragraphs describe some of the general functions performed by each of layers 110-120 in BMS 100.
Enterprise integration layer 110 can be configured to serve clients or local applications with information and services to support a variety of enterprise-level applications. For example, enterprise control applications 126 can be configured to provide subsystem-spanning control to a graphical user interface (GUI) or to any number of enterprise-level business applications (e.g., accounting systems, user identification systems, etc.). Enterprise control applications 126 can also or alternatively be configured to provide configuration GUIs for configuring BMS controller 101. In yet other embodiments, enterprise control applications 126 can work with layers 110-120 to optimize building performance (e.g., efficiency, energy use, comfort, or safety) based on inputs received at interface 107 and/or BMS interface 109.
Building subsystem integration layer 120 can be configured to manage communications between BMS controller 101 and building subsystems 128. For example, building subsystem integration layer 120 can receive sensor data and input signals from building subsystems 128 and provide output data and control signals to building subsystems 128. Building subsystem integration layer 120 can also be configured to manage communications between building subsystems 128. Building subsystem integration layer 120 translates communications (e.g., sensor data, input signals, output signals, etc.) across a plurality of multi-vendor/multi-protocol systems.
Demand response layer 114 can be configured to optimize resource usage (e.g., electricity use, natural gas use, water use, etc.) and/or the monetary cost of such resource usage in response to satisfy the demand of a building. The optimization can be based on time-of-use prices, curtailment signals, energy availability, or other data received from utility providers, distributed energy generation systems 124, from energy storage 127, or from other sources. Demand response layer 114 can receive inputs from other layers of BMS controller 101 (e.g., building subsystem integration layer 120, integrated control layer 118, etc.). The inputs received from other layers can include environmental or sensor inputs such as temperature, carbon dioxide levels, relative humidity levels, air quality sensor outputs, occupancy sensor outputs, room schedules, and the like. The inputs can also include inputs such as electrical use (e.g., expressed in kWh), thermal load measurements, pricing information, projected pricing, smoothed pricing, curtailment signals from utilities, and the like.
According to an exemplary embodiment, demand response layer 114 includes control logic for responding to the data and signals it receives. These responses can include communicating with the control algorithms in integrated control layer 118, changing control strategies, changing setpoints, or activating/deactivating building equipment or subsystems in a controlled manner. Demand response layer 114 can also include control logic configured to determine when to utilize stored energy. For example, demand response layer 114 can determine to begin using energy from energy storage 127 just prior to the beginning of a peak use hour.
In some embodiments, demand response layer 114 includes a control module configured to actively initiate control actions (e.g., automatically changing setpoints) which minimize energy costs based on one or more inputs representative of or based on demand (e.g., price, a curtailment signal, a demand level, etc.). In some embodiments, demand response layer 114 uses equipment models to determine an optimal set of control actions. The equipment models can include, for example, thermodynamic models describing the inputs, outputs, and/or functions performed by various sets of building equipment. Equipment models can represent collections of building equipment (e.g., subplants, chiller arrays, etc.) or individual devices (e.g., individual chillers, heaters, pumps, etc.).
Demand response layer 114 can further include or draw upon one or more demand response policy definitions (e.g., databases, XML files, etc.). The policy definitions can be edited or adjusted by a user (e.g., via a graphical user interface) so that the control actions initiated in response to demand inputs can be tailored for the user's application, desired comfort level, particular building equipment, or based on other concerns. For example, the demand response policy definitions can specify which equipment can be turned on or off in response to particular demand inputs, how long a system or piece of equipment should be turned off, what setpoints can be changed, what the allowable set point adjustment range is, how long to hold a high demand set-point before returning to a normally scheduled set-point, how close to approach capacity limits, which equipment modes to utilize, the energy transfer rates (e.g., the maximum rate, an alarm rate, other rate boundary information, etc.) into and out of energy storage devices (e.g., thermal storage tanks, battery banks, etc.), and when to dispatch on-site generation of energy (e.g., via fuel cells, a motor generator set, etc.).
Integrated control layer 118 can be configured to use the data input or output of building subsystem integration layer 120 and/or demand response later 114 to make control decisions. Due to the subsystem integration provided by building subsystem integration layer 120, integrated control layer 118 can integrate control activities of the subsystems 128 such that the subsystems 128 behave as a single integrated supersystem. In an exemplary embodiment, integrated control layer 118 includes control logic that uses inputs and outputs from a plurality of building subsystems to provide greater comfort and energy savings relative to the comfort and energy savings that separate subsystems could provide alone. For example, integrated control layer 118 can be configured to use an input from a first subsystem to make an energy-saving control decision for a second subsystem. Results of these decisions can be communicated back to building subsystem integration layer 120.
Integrated control layer 118 is shown to be logically below demand response layer 114. Integrated control layer 118 can be configured to enhance the effectiveness of demand response layer 114 by enabling building subsystems 128 and their respective control loops to be controlled in coordination with demand response layer 114. This configuration may advantageously reduce disruptive demand response behavior relative to conventional systems. For example, integrated control layer 118 can be configured to assure that a demand response-driven upward adjustment to the set-point for chilled water temperature (or another component that directly or indirectly affects temperature) does not result in an increase in fan energy (or other energy used to cool a space) that would result in greater total building energy use than was saved at the chiller.
Integrated control layer 118 can be configured to provide feedback to demand response layer 114 so that demand response layer 114 checks that constraints (e.g., temperature, lighting levels, etc.) are properly maintained even while demanded load shedding is in progress. The constraints can also include set-point or sensed boundaries relating to safety, equipment operating limits and performance, comfort, fire codes, electrical codes, energy codes, and the like. Integrated control layer 118 is also logically below fault detection and diagnostics layer 116 and automated measurement and validation layer 112. Integrated control layer 118 can be configured to provide calculated inputs (e.g., aggregations) to these higher levels based on outputs from more than one building subsystem.
Automated measurement and validation (AM&V) layer 112 can be configured to verify that control strategies commanded by integrated control layer 118 or demand response layer 114 are working properly (e.g., using data aggregated by AM&V layer 112, integrated control layer 118, building subsystem integration layer 120, FDD layer 116, or otherwise). The calculations made by AM&V layer 112 can be based on building system energy models and/or equipment models for individual BMS devices or subsystems. For example, AM&V layer 112 can compare a model-predicted output with an actual output from building subsystems 128 to determine an accuracy of the model.
Fault detection and diagnostics (FDD) layer 116 can be configured to provide on-going fault detection for building subsystems 128, building subsystem devices (i.e., building equipment), and control algorithms used by demand response layer 114 and integrated control layer 118. FDD layer 116 can receive data inputs from integrated control layer 118, directly from one or more building subsystems or devices, or from another data source. FDD layer 116 can automatically diagnose and respond to detected faults. The responses to detected or diagnosed faults can include providing an alert message to a user, a maintenance scheduling system, or a control algorithm configured to attempt to repair the fault or to work-around the fault.
FDD layer 116 can be configured to output a specific identification of the faulty component or cause of the fault (e.g., loose damper linkage) using detailed subsystem inputs available at building subsystem integration layer 120. In other exemplary embodiments, FDD layer 116 is configured to provide “fault” events to integrated control layer 118 which executes control strategies and policies in response to the received fault events. According to an exemplary embodiment, FDD layer 116 (or a policy executed by an integrated control engine or business rules engine) can shut-down systems or direct control activities around faulty devices or systems to reduce energy waste, extend equipment life, or ensure proper control response.
FDD layer 116 can be configured to store or access a variety of different system data stores (or data points for live data). FDD layer 116 can use some content of the data stores to identify faults at the equipment level (e.g., specific chiller, specific AHU, specific terminal unit, etc.) and other content to identify faults at component or subsystem levels. For example, building subsystems 128 can generate temporal (i.e., time-series) data indicating the performance of BMS 100 and the various components thereof. The data generated by building subsystems 128 can include measured or calculated values that exhibit statistical characteristics and provide information about how the corresponding system or process (e.g., a temperature control process, a flow control process, etc.) is performing in terms of error from its set-point. These processes can be examined by FDD layer 116 to expose when the system begins to degrade in performance and alert a user to repair the fault before it becomes more severe.
Referring now to
User interface system 202 may generally be configured to generate an interactive user interface for display on a user device 204. The interactive user interface may generally display information relating to a particular object (e.g., a piece of equipment of a building subsystem, a building area, etc.) and the relationship between the object and other objects in the building. In the present disclosure, the term “object” is used to describe a particular piece of equipment, building area, or other individual aspect associated with a BMS (e.g., BMS 100); and it should be understood that the term is not limiting towards the type of information associated with the object.
User device 204 may be, for example, a workstation, a desktop, a laptop, a tablet, or a mobile device. In various embodiments, user device 204 may include a keyboard, a mouse, a touchscreen, or any other component for allowing the user to provide an input to user interface system 202. User device 204 may include any type of display, and user interface system 202 may generally be configured to generate a user interface compatible with the type of user device 204 wishing to access the user interface.
BMS controller 101 is shown to include various databases storing information relating to the various components of BMS 100. In some embodiments, the databases may be located and maintained within BMS controller 101; in other embodiments, the databases may be located remotely from BMS controller 101, and may be accessed by BMS controller 101 via a wired or wireless connection. Further, while each database shown in
BMS controller 101 may include an equipment database 210 storing information relating to individual pieces of equipment in BMS 100. Equipment database 210 may store, for each piece of equipment, one or more subsystems to which the piece of equipment belongs, along with information about the functionality and operating parameters of the equipment. The information stored in equipment database 210 may further include relationships between different pieces of equipment. For example, for a given piece of equipment for a building subsystem, the other equipment in the building subsystem may be identified. When information about the equipment is then retrieved (i.e., by user interface system 202), the information may include the relationship the equipment has with other equipment in BMS 100.
BMS controller 101 may include a building space database 212 storing information relating to individual building spaces in the building. Building space database 212 may store information identifying each room in a building, each floor in a building, and multiple rooms, floors, or areas which are related to one another. For example, multiple rooms in a building may share a common area, the environment in a first room may impact the environment in a second room, and so forth. Building space database 212 may store information about each building area in a building and how the building areas are related.
BMS controller 101 may include a control logic database 214 storing information relating to the control of the various equipment and subsystems in BMS 100. Control logic database 214 may store, for example, high level control logic for BMS 100. The high level control logic may relate to a general strategy for operation of equipment in BMS 100. For example, BMS 100 may implement an energy savings strategy and may provide control logic for the various building subsystems to cause the building subsystems to use less power during operation. As another example, BMS 100 may implement control logic for a specific building subsystem (i.e., control logic to specifically control the temperature within the building via the HVAC system). Referring generally to the present disclosure, “high level control logic” may relate to control logic for all equipment in a building, for a particular subset of equipment in a building, or one or more specific building subsystems, or any combination thereof. In various embodiments, one or more BMS controllers may update the control logic for BMS 100 based on the current conditions and/or user input, and user interface system 202 may retrieve the updated control logic via control logic database 214 or via any other method.
BMS controller 101 may include a setpoint database 216 storing information relating to one or more setpoints for one or more building areas or spaces in the building. For example, setpoint database 216 may include one or more settings for a space (e.g., a temperature or other condition to be maintained in a building area). Setpoint database 216 may further include one or more settings for the operation of one or more pieces of equipment in BMS 100.
User interface system 202 is shown to include various modules for creating and updating an interactive user interface to be provided to user device 204. User interface system 202 is shown to include a user input module 220 configured to receive a user input via user device 204 and to interpret the input. For example, the user input may relate to the selection of a specific piece of equipment or specific building area to be displayed on the user interface. User input module 220 may be configured to identify the object associated with the user input (e.g., an object representing the piece of equipment or building area specified) and to identify other objects related to the object. The user may be configured to provide the user input via any type of selection (e.g., the selection of a link on the user interface, a selection from a menu, a text entry, a selection via a touch on a touchscreen, etc.).
User interface system 202 is further shown to include a data retrieval module 222. Based on the user input (as described in user input module 220), data retrieval module 222 may identify other pieces of equipment, and/or other building areas related to the identified object. Data retrieval module 222 may then retrieve data relevant to each of the equipment and spaces from databases 210-216 and other sources. Data retrieval module 222 may further retrieve data relating to a current status of the equipment and spaces. For example, data retrieval module 222 may retrieve performance data for a piece of equipment, the current environment (e.g., temperature) in a building area, and the like.
User interface system 202 is further shown to include an object relationship module 224. Using the identified object and the identified related equipment and spaces, object relationship module 224 may determine a relationship between the various components. Further, using data retrieved by data retrieval module 222, object relationship module 224 may determine which components have an impact on particular data points. For example, for a temperature data point for a building area, object relationship module 224 may identify all equipment used in maintaining the temperature in the building area.
Referring also to
Data retrieval module 222, based on the selection of object 302, may retrieve information, such as a schedule 304. Schedule 304 may indicate a desired temperature level for a building area over time. Schedule 304 may be set based on a general control strategy for a building, and may impact any number of building areas. For example, schedule 304 may be a schedule for a single piece of equipment, for all equipment in a building area, or for all areas in a building. Therefore, the information retrieved by data retrieval module 222 may include an indication that a change in the schedule may impact just a single building area or multiple building areas.
Object relationship module 224 may identify one or more values or setpoints which may be impacted by the AHU. For example, object relationship module 224 may identify a current temperature in a building area that the AHU is partially responsible for maintaining. Further, object relationship module 224 may identify a setpoint to be achieved in a building area that the AHU is partially responsible for maintaining. In the example of
Object relationship module 224, using the information and the identified values and setpoints, may provide an output 306 specifying one or more equipment, setpoints, or control strategies impacted by the object. In other words, object relationship module 224 identifies the components of BMS 100 that are impacted by the performance of the AHU. In the example shown in
User interface system 202 is further shown to include a display module 226 configured to generate the interactive user interface on user device 204. Display module 226 may generally be configured to provide a layout identifying the object selected by the user and objects for associated equipment and spaces. Display module 226 may show the link between the various components in any way. In various embodiments, the interactive user interface may make each object selectable in any way (e.g., via a link, button, menu option, via touchscreen, etc.).
Display module 226 may be configured to generate different layouts for different types of user devices. For example, referring to
For a mobile device or other device with a relatively small display, a layout similar to that shown in
As yet another example of an output from display module 226, the user interface may have a similar structure as that shown in
Referring generally to
Object 502 representing the hot water system is shown to display a list of spaces served by the hot water system. Object 502 may identify multiple spaces 504. Object 502 may further identify multiple networks 506, i.e., one or more networks to which the hot water system is connected. Each individual space 504 and network 506 are shown to be selectable via link. Upon selection of a space or network, user interface 500 may be configured to create an object for the space or network and to display all components affected by the space or network. This allows the user to navigate from component to component via user interface 500.
User interface 500 further illustrates various components (e.g., equipment, setpoints, etc.) that impact the performance of the hot water system. For example, a boiler 510 of the hot water system is shown as enabled (BLR-ENA) with a low priority level (16). Boiler 510 is an example of a piece of equipment associated with the hot water system. A hot water pump status 512 (HWP6-S) is shown, with an alarm generated based on a current value 522. A hot water supply differential pressure (HWS-DP) value 514 is shown, also with an alarm generated based on the current value. Status 512 and value 514 are example values of current conditions that the hot water system may be responsible for maintaining or monitoring.
Further, a boiler discharge value 516 (BLR2-DIS) is shown as true. In this example, an operator has provided an override value to BMS 100 based on the status of the boiler. User interface 500 may indicate that the operator has provided the override value, and that the override value has an impact on the status of the hot water system.
Further, a second hot water pump status 518 is shown (HWP5-S), with an alarm generated based on a current value. User interface 500 may highlight object 518 on the screen to further illustrate its impact on the hot water heater. User interface 500 may be configured to highlight each object on the screen in various ways (e.g., via shading, coloring, different line weights or dashes, different shapes, different text, etc.).
In the embodiment of
User interface 500 further illustrates an output 520 of the hot water system (HWP5-O). As the user modifies a value, setting, or control strategy, user interface 500 may update to show an updated output 520, allowing the user to see how a change in one component impacts an output of the hot water system.
Referring to
Referring to
Referring now to
As the AHU is a piece of equipment, data may be retrieved for display on user interface 800 that may impact the performance or operation of the AHU. For example, outside air temperature 810 (OA-T) is shown as an identified data point relevant to the AHU. The outside air temperature may generally impact the control strategy for the AHU, as the temperature may impact the decision on whether the AHU needs to provide cooled or heated air to a building area. Outside air temperature 810 (shown as 70°) is shown associated with a building area (BLDG3610).
As shown in
Referring to
Referring further to
As described with reference to
Some objects may be highlighted (922) in user interface 900. This is illustrated in
Referring now to
Process 1000 includes receiving a user query including the selection of a first object (1002). The first object may be associated with one of a building system, a piece of equipment, or a space in the building. The selection may be an indication from a user that the user wishes to view the relationship between the object and other objects in a BMS.
Process 1000 includes determining one or more pieces of equipment impacted by the first object (1004). For example, if the first object represents a building space, 1004 may include identifying all equipment in the building space. If the first object represents a building subsystem, 1004 may include identifying all equipment part of the subsystem. If the first object represents a piece of equipment, 1004 may include identifying all equipment connected to the identified equipment.
Process 1000 includes determining an effect of the first object on control logic on the one or more pieces of equipment (1006). As described in the present disclosure, the subsystems and equipment of the BMS may be controlled by a high level control logic. 1006 may include identifying potential changes to the high level control logic to account for the behavior of the first object.
Process 1000 includes determining one or more building spaces impacted by the first object (1008). Process 1000 includes determining one or more setpoints of the one or more spaces (1010). The setpoints may include, for example, a condition that a piece of equipment or subsystem is supposed to maintain. For example, a setpoint may include a temperature setpoint for the space, lighting levels for the space, and the like.
Process 1000 includes determining one or more values associated with the first object, one or more pieces of equipment, and one or more spaces (1012). Values may include, for example, a current status of a piece of equipment or space, current environmental conditions in a space, a warning status for a piece of equipment or space, or parameters for the operation of a piece of equipment. The values may include “real-time” values of the current environment, or current settings associated with an equipment or space.
Process 1000 includes generating a user interface illustrating the first object and its relationship with the one or more equipment and spaces (1014). The relationship may be illustrated using, for example, by defining a control path between the equipment and spaces. Each equipment and space may be represented by an object in the user interface. The object may be a link, icon, button, or any other feature on the user interface that may be interacted with by a user. The user interface may further include the values determined at 1012. For example, values associated with a particular object may be displayed next to the object, allowing the user to view an impact of the first object on the values.
In some embodiments, the query received at 1002 may include a change in operation of the first object, or a change in a setpoint or value associated with the first object. The subsequent portions of process 1000 may then further include determining an effect in control logic and setpoints that the change has.
In some implementations, the user may be provided with a schedule via the user interface. The schedule may relate to the implementation of control logic for a piece of equipment, or a schedule of setpoints for a building area. The user may be able to view adjustments in the schedule based on the impact that the first object has on the schedule.
According to the exemplary embodiment shown in
As shown in
The selected object section 1130 includes a first object indicia or box, shown as selected object box 1132, that is displayed by the BMS 100 and/or the user interface system 202 in the involvement map 1122 based on the user selection of an object of interest (e.g., a respective object 1114 in the network tree 1112). The selected object box 1132 represents an item or component (e.g., a piece of equipment, a building area, a subsystem, etc.) associated with or included in the BMS 100. The selected object box 1132 is then used by the BMS 100 and/or the user interface system 202 as the basis for relationships and involvements determined, acquired, and/or generated by the BMS 100 and/or the user interface system 202 and displayed through the remainder of the involvement map 1122. For example, the relationships and involvements of the item or component represented by the selected object box 1132 may be read from the item or component associated with the BMS 100, the respective object 1114 selected, and/or the selected object box 1132 (e.g., based on a user configuration of the item or component associated with the selected object box 1132, based on a user configuration of the respective object 1114, based on a user configuration of the selected object box 1132) and displayed to a user via the involvement map 1122.
After selection of a respective object associated with an item or component associated with the BMS 100 (e.g., through the network tree 1112) and displaying the selected object box 1132 associated therewith, the BMS 100 and/or the user interface system 202 are configured to acquire the relationships and involvements associated with the item, component, or object represented by the selected object box 1132 and populate the upstream object section 1140 and the downstream object section 1150 accordingly. Specifically, as shown in
The upstream object boxes 1142 represent respective objects (e.g., from the network tree 1112, the objects 1114, which represent items or components associated with or included in the BMS 100, etc.) that have some sort of upstream relationship and/or involvement with the selected object box 1132 (or the respective object 1114 or the item/component associated therewith). In some embodiments, an upstream relationship and/or involvement with the selected object box 1132 indicates that the building objects represented by the upstream object boxes 1142 are located physically or logically “upstream” of the building object represented by the selected object box 1132 in the BMS 100. Upstream building objects represented by the upstream object boxes 1142 may operate in a manner that affects the building object represented by the selected object box 1132. For example, if the building object represented by the selected object box 1132 is a VAV unit or building space, an upstream controller or AHU represented by the upstream object boxes 1142 may operate in a manner that controls operation of the VAV unit represented by the selected object box 1132 or affects a temperature or humidity of the building space represented by the selected object box 1132. Upstream building objects represented by the upstream object boxes 1142 may be include building objects that are referenced by the building object represented by the selected object box 1132. For example, the building object represented by the selected object box 1132 may reference one or more attributes of the upstream building objects represented by the upstream object boxes 1142 such that one or more attributes of the building object represented by the selected object box 1132 are logically dependent upon one or more attributes of the upstream building objects represented by the upstream object boxes 1142.
The downstream object boxes 1152 represent respective objects (e.g., from the network tree 1112, the objects 1114, which represent items or components associated with or included in the BMS 100, etc.) that have some sort of downstream relationship and/or involvement with the selected object box 1132 (or the respective object 1114 or the item/component associated therewith). In some embodiments, a downstream relationship and/or involvement with the selected object box 1132 indicates that the building objects represented by the downstream object boxes 1152 are located physically or logically “downstream” of the building object represented by the selected object box 1132 in the BMS 100. Downstream building objects represented by the downstream object boxes 1152 may be affected by operation of the building object represented by the selected object box 1132. For example, if the building object represented by the selected object box 1132 is a controller or AHU, a downstream VAV unit or building space represented by the downstream object boxes 1152 may be controlled by the controller represented by the selected object box 1132 or the temperature or humidity of the building space may be affected by operation of the AHU represented by the selected object box 1132. Downstream building objects represented by the upstream object boxes 1152 may be include building objects that reference the building object represented by the selected object box 1132. For example, the building object represented by the selected object box 1132 may include one or more attributes that are referenced by the downstream building objects represented by the downstream object boxes 1152 such that one or more attributes of the building objects represented by the downstream object boxes 1152 are logically dependent upon one or more attributes of the building object represented by the selected object box 1132.
As shown in
As shown in
The “referenced by” involvement 1160 indicates that the selected object box 1132 is involved with a respective upstream object box 1142 or a respective downstream object box 1152 through a referential relationship/involvement where one object associated with one of the two boxes involved in the relationship (i.e., connected by a respective upstream relationship line 1144, connected by a respective downstream relationship line 1154) references the other object associated with the other one of the two boxes involved in the relationship. As an example, as shown in
The “controls” involvement 1162 indicates that the selected object box 1132 is involved with a respective upstream object box 1142 or a respective downstream object box 1152 through a controls relationship where one object associated with one of the two boxes involved in the relationship (i.e., connected by a respective upstream relationship line 1144, connected by a respective downstream relationship line 1154) controls the other object associated with the other one of the two boxes involved in the relationship is some way (e.g., a write control, a command control, etc.). As an example, as shown in
As shown in
The “unbound” involvement 1168 indicates that the selected object box 1132 was previously involved with a respective upstream object box 1142 or a respective downstream object box 1152 (e.g., through a “referenced by” involvement 1160, through a “controls” involvement 1162, etc.), but such involvement or relationship has been severed or otherwise removed (e.g., intentionally, unintentionally, etc.). As an example, as shown in
While the involvement types described herein have been referred to as being either a “referenced by” involvement, a “controls” involvement, or an “unbound” involvement, it should be understood that other types of involvements may exist or be implemented to provide and define different types of relationships between the objects of the involvement map 1122.
As shown in
As shown in
In some embodiments, the BMS 100 and/or the user interface system 202 are configured to obtain or generate various information associated with each of the building objects represented by the boxes of the involvement map (e.g., current status, attributes, failure conditions, operator override conditions, threshold evaluations, rule comparisons, operating conditions, etc.) and generate the notifications 1180 within each of the boxes of the involvement map 1122 based on the information for the respective building objects. The notifications 1180 can be provided within the boxes, adjacent to the boxes, or otherwise provided in connection with the boxes of the involvement map 1122 to convey various information about the respective building objects to the user within the user interface shown in
While the present disclosure has been described in the context of implementing the involvement GUI 1100 using the BMS 100 and user interface system 202 architecture, it is contemplated that a variety of different types of system architectures may be implemented to provide the involvement GUI 1100. For example, the building data platform and the twin manager (i) described in (a) U.S. Patent Publication No. 2022/0405327, filed Jun. 22, 2021, and (b) International Patent Publication No. WO2021/138245, filed Dec. 28, 2020, both of which are incorporated herein by reference in their entireties, and (ii) described below with respect to
In some embodiments, the BMS 100 and/or the user interface system 202 generates the involvement GUI 1100 based on a digital twin of the BMS 100. For example, in response to receiving a selection of a first object (e.g., an object representing a particular piece of equipment, space, point, or other entity in the BMS 100), the user interface system 202 can query a digital twin of the BMS to identify an entity that corresponds to the first object (e.g., an entity that represents the same piece of equipment, space, point, etc. represented by the first object). The user interface system 202 can then identify any relationships (e.g., connections, edges, etc.) between the identified entity (i.e., the “first entity”) and other entities in the digital twin of the BMS 100, as well as the other entities connected to the first entity. The user interface system 202 can extract the other entities and the relationships from the digital twin of the BMS 100 and use the extracted entities and relationships to populate the involvement GUI 1100. For example, the other entities connected to the first entity in the digital twin of the BMS 100 can be used to populate the second objects associated with the first object in the involvement GUI 1100. Similarly, the relationships connecting the first entity to the other entities in the digital twin of the BMS 100 can be used to populate the particular types of connections and connector lines in the involvement GUI 1100 between the first object and the second objects.
Using a digital twin of the BMS 100 to generate the involvement GUI 1100 provides several advantages over other types of graph data structures with entities and relationships. For example, the digital twin can be kept up-to-date by processing relationships and telemetry changes that happen within the building (e.g., in real-time, periodically, in response to detecting such changes, etc.). Accordingly, any changes to the relationships or objects in the BMS 100 can be automatically and rapidly reflected in the digital twin by making corresponding changes to the particular relationships and entities in the digital twin. Therefore, whenever the digital twin is queried to identify particular objects and connections associated with the first object in the involvement GUI 1100, the query result will be up-to-date and reflects the current state of the digital twin, which in turn reflects the current state of the BMS 100. The current state of the digital twin has an effect on the results of the involvement queries and relationships described herein, and therefore keeping the digital twin up-to-date ensures that the results of the involvement queries are up-to-date as well. These and other advantages provided by the digital twin are described in greater detail with reference to
Referring now to
The building data platform 2100 includes applications 2110. The applications 2110 can be various applications that operate to manage the building subsystems 2122. The applications 2110 can be remote or on-premises applications (or a hybrid of both) that run on various computing systems. The applications 2110 can include an alarm application 2168 configured to manage alarms for the building subsystems 2122. The applications 2110 include an assurance application 2170 that implements assurance services for the building subsystems 2122. In some embodiments, the applications 2110 include an energy application 2172 configured to manage the energy usage of the building subsystems 2122. The applications 2110 include a security application 2174 configured to manage security systems of the building.
In some embodiments, the applications 2110 and/or the cloud platform 2106 interacts with a user device 2176. In some embodiments, a component or an entire application of the applications 2110 runs on the user device 2176. The user device 2176 may be a laptop computer, a desktop computer, a smartphone, a tablet, and/or any other device with an input interface (e.g., touch screen, mouse, keyboard, etc.) and an output interface (e.g., a speaker, a display, etc.).
The applications 2110, the twin manager 2108, the cloud platform 2106, and the edge platform 2102 can be implemented on one or more computing systems, e.g., on processors and/or memory devices. For example, the edge platform 2102 includes processor(s) 2118 and memories 2120, the cloud platform 2106 includes processor(s) 2124 and memories 2126, the applications 2110 include processor(s) 2164 and memories 2166, and the twin manager 2108 includes processor(s) 2148 and memories 2150.
The processors can be a general purpose or specific purpose processors, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable processing components. The processors may be configured to execute computer code and/or instructions stored in the memories or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc.).
The memories can include one or more devices (e.g., memory units, memory devices, storage devices, etc.) for storing data and/or computer code for completing and/or facilitating the various processes described in the present disclosure. The memories can include random access memory (RAM), read-only memory (ROM), hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. The memories can include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. The memories can be communicably connected to the processors and can include computer code for executing (e.g., by the processors) one or more processes described herein.
The edge platform 2102 can be configured to provide connection to the building subsystems 2122. The edge platform 2102 can receive messages from the building subsystems 2122 and/or deliver messages to the building subsystems 2122. The edge platform 2102 includes one or multiple gateways, e.g., the gateways 2112-2116. The gateways 2112-2116 can act as a gateway between the cloud platform 2106 and the building subsystems 2122. The gateways 2112-2116 can be the gateways described in U.S. Patent Publication No. 2021/0191826, filed Dec. 18, 2020, which is incorporated herein by reference in its entirety. In some embodiments, the applications 2110 can be deployed on the edge platform 2102. In this regard, lower latency in management of the building subsystems 2122 can be realized.
The edge platform 2102 can be connected to the cloud platform 2106 via a network 2104. The network 2104 can communicatively couple the devices and systems of building data platform 2100. In some embodiments, the network 2104 is at least one of and/or a combination of a Wi-Fi network, a wired Ethernet network, a ZigBee network, a Bluetooth network, and/or any other wireless network. The network 2104 may be a local area network or a wide area network (e.g., the Internet, a building WAN, etc.) and may use a variety of communications protocols (e.g., BACnet, IP, LON, etc.). The network 2104 may include routers, modems, servers, cell towers, satellites, and/or network switches. The network 2104 may be a combination of wired and wireless networks.
The cloud platform 2106 can be configured to facilitate communication and routing of messages between the applications 2110, the twin manager 2108, the edge platform 2102, and/or any other system. The cloud platform 2106 can include a platform manager 2128, a messaging manager 2140, a command processor 2136, and an enrichment manager 2138. In some embodiments, the cloud platform 2106 can facilitate messaging between the building data platform 2100 via the network 2104.
The messaging manager 2140 can be configured to operate as a transport service that controls communication with the building subsystems 2122 and/or any other system, e.g., managing commands to devices (C2D), commands to connectors (C2C) for external systems, commands from the device to the cloud (D2C), and/or notifications. The messaging manager 2140 can receive different types of data from the applications 2110, the twin manager 2108, and/or the edge platform 2102. The messaging manager 2140 can receive change on value data 2142, e.g., data that indicates that a value of a point has changed. The messaging manager 2140 can receive timeseries data 2144, e.g., a time correlated series of data entries each associated with a particular time stamp. Furthermore, the messaging manager 2140 can receive command data 2146. All of the messages handled by the cloud platform 2106 can be handled as an event, e.g., the data 2142-2146 can each be packaged as an event with a data value occurring at a particular time (e.g., a temperature measurement made at a particular time).
The cloud platform 2106 includes a command processor 2136. The command processor 2136 can be configured to receive commands to perform an action from the applications 2110, the building subsystems 2122, the user device 2176, etc. The command processor 2136 can manage the commands, determine whether the commanding system is authorized to perform the particular commands, and communicate the commands to the commanded system, e.g., the building subsystems 2122 and/or the applications 2110. The commands could be a command to change an operational setting that control environmental conditions of a building, a command to run analytics, etc.
The cloud platform 2106 includes an enrichment manager 2138. The enrichment manager 2138 can be configured to enrich the events received by the messaging manager 2140. The enrichment manager 2138 can be configured to add contextual information to the events. The enrichment manager 2138 can communicate with the twin manager 2108 to retrieve the contextual information. In some embodiments, the contextual information is an indication of information related to the event. For example, if the event is a timeseries temperature measurement of a thermostat, contextual information such as the location of the thermostat (e.g., what room), the equipment controlled by the thermostat (e.g., what VAV), etc. can be added to the event. In this regard, when a consuming application, e.g., one of the applications 2110 receives the event, the consuming application can operate based on the data of the event, the temperature measurement, and also the contextual information of the event.
The enrichment manager 2138 can solve a problem that when a device produces a significant amount of information, the information may contain simple data without context. An example might include the data generated when a user scans a badge at a badge scanner of the building subsystems 2122. This physical event can generate an output event including such information as “DeviceBadgeScannerID,” “BadgeID,” and/or “Date/Time.” However, if a system sends this data to a consuming application, e.g., Consumer A and a Consumer B, each customer may need to call the building data platform knowledge service to query information with queries such as, “What space, build, floor is that badge scanner in?” or “What user is associated with that badge?”
By performing enrichment on the data feed, a system can be able to perform inferences on the data. A result of the enrichment may be transformation of the message “DeviceBadgeScannerId, BadgeId, Date/Time,” to “Region, Building, Floor, Asset, DeviceId, BadgeId, UserName, EmployeeId, Date/Time Scanned.” This can be a significant optimization, as a system can reduce the number of calls by 1/n, where n is the number of consumers of this data feed.
By using this enrichment, a system can also have the ability to filter out undesired events. If there are 100 building in a campus that receive 100,000 events per building each hour, but only 1 building is actually commissioned, only 1/10 of the events are enriched. By looking at what events are enriched and what events are not enriched, a system can do traffic shaping of forwarding of these events to reduce the cost of forwarding events that no consuming application wants or reads.
An example of an event received by the enrichment manager 2138 may be:
An example of an enriched event generated by the enrichment manager 2138 may be:
By receiving enriched events, an application of the applications 2110 can be able to populate and/or filter what events are associated with what areas. Furthermore, user interface generating applications can generate user interfaces that include the contextual information based on the enriched events.
The cloud platform 2106 includes a platform manager 2128. The platform manager 2128 can be configured to manage the users and/or subscriptions of the cloud platform 2106. For example, what subscribing building, user, and/or tenant utilizes the cloud platform 106. The platform manager 2128 includes a provisioning service 2130 configured to provision the cloud platform 2106, the edge platform 2102, and the twin manager 2108. The platform manager 2128 includes a subscription service 2132 configured to manage a subscription of the building, user, and/or tenant while the entitlement service 2134 can track entitlements of the buildings, users, and/or tenants.
The twin manager 2108 can be configured to manage and maintain a digital twin. The digital twin can be a digital representation of the physical environment, e.g., a building. The twin manager 2108 can be configured to maintain the digital twin in an up-to-date state by processing relationships and telemetry changes that occur within the building (e.g., continuously, periodically, in real-time, etc.). The twin manager 2108 can include a change feed generator 2152, a schema and ontology 2154, a projection manager 2156, a policy manager 2158, an entity, relationship, and event database 2160, and a graph projection database 2162.
The graph projection manager 2156 can be configured to construct graph projections and store the graph projections in the graph projection database 2162 (e.g., by processing relationships and telemetry changes within the building). Entities, relationships, and events can be stored in the database 2160. The graph projection manager 2156 can retrieve entities, relationships, and/or events from the database 2160 and construct a graph projection based on the retrieved entities, relationships and/or events. In some embodiments, the database 2160 includes an entity-relationship collection for multiple subscriptions. Subscriptions can be subscriptions of a particular tenant.
In some embodiment, the graph projection manager 2156 generates a graph projection for a particular user, application, subscription, and/or system. In this regard, the graph projection can be generated based on policies for the particular user, application, and/or system in addition to an ontology specific for that user, application, and/or system. In this regard, an entity could request a graph projection and the graph projection manager 2156 can be configured to generate the graph projection for the entity based on policies and an ontology specific to the entity. The policies can indicate what entities, relationships, and/or events the entity has access to. The ontology can indicate what types of relationships between entities the requesting entity expects to see, e.g., floors within a building, devices within a floor, etc. Another requesting entity may have an ontology to see devices within a building and applications for the devices within the graph.
The graph projections generated by the graph projection manager 2156 and stored in the graph projection database 2162 can be a knowledge graph and is an integration point. For example, the graph projections can represent floor plans and systems associated with each floor. Furthermore, the graph projections can include events, e.g., telemetry data of the building subsystems 2122. The graph projections can show application services as nodes and API calls between the services as edges in the graph. The graph projections can illustrate the capabilities of spaces, users, and/or devices. The graph projections can include indications of the building subsystems 2122, e.g., thermostats, cameras, VAVs, etc. The graph projection database 2162 can store graph projections that keep up a current state of a building.
The graph projections of the graph projection database 2162 can be digital twins of a building. Digital twins can be digital replicas of physical entities that enable an in-depth analysis of data of the physical entities and provide the potential to monitor systems to mitigate risks, manage issues, and utilize simulations to test future solutions. Digital twins can play an important role in helping technicians find the root cause of issues and solve problems faster, in supporting safety and security protocols, and in supporting building managers in more efficient use of energy and other facilities resources. Digital twins can be used to enable and unify security systems, employee experience, facilities management, sustainability, etc.
In some embodiments the enrichment manager 2138 can use a graph projection of the graph projection database 2162 to enrich events. In some embodiments, the enrichment manager 2138 can identify nodes and relationships that are associated with, and are pertinent to, the device that generated the event. For example, the enrichment manager 2138 could identify a thermostat generating a temperature measurement event within the graph. The enrichment manager 2138 can identify relationships between the thermostat and spaces, e.g., a zone that the thermostat is located in. The enrichment manager 2138 can add an indication of the zone to the event.
Furthermore, the command processor 2136 can be configured to utilize the graph projections to command the building subsystems 2122. The command processor 2136 can identify a policy for a commanding entity within the graph projection to determine whether the commanding entity has the ability to make the command. For example, the command processor 2136, before allowing a user to make a command, determine, based on the graph projection database 2162, to determine that the user has a policy to be able to make the command.
In some embodiments, the policies can be conditional based policies. For example, the building data platform 2100 can apply one or more conditional rules to determine whether a particular system has the ability to perform an action. In some embodiments, the rules analyze a behavioral based biometric. For example, a behavioral based biometric can indicate normal behavior and/or normal behavior rules for a system. In some embodiments, when the building data platform 2100 determines, based on the one or more conditional rules, that an action requested by a system does not match a normal behavior, the building data platform 2100 can deny the system the ability to perform the action and/or request approval from a higher level system.
For example, a behavior rule could indicate that a user has access to log into a system with a particular IP address between 8 A.M. through 5 P.M. However, if the user logs in to the system at 7 P.M., the building data platform 2100 may contact an administrator to determine whether to give the user permission to log in.
The change feed generator 2152 can be configured to generate a feed of events that indicate changes to the digital twin, e.g., to the graph. The change feed generator 2152 can track changes to the entities, relationships, and/or events of the graph. For example, the change feed generator 2152 can detect an addition, deletion, and/or modification of a node or edge of the graph, e.g., changing the entities, relationships, and/or events within the database 2160. In response to detecting a change to the graph, the change feed generator 2152 can generate an event summarizing the change. The event can indicate what nodes and/or edges have changed and how the nodes and edges have changed. The events can be posted to a topic by the change feed generator 2152.
The change feed generator 2152 can implement a change feed of a knowledge graph. The building data platform 2100 can implement a subscription to changes in the knowledge graph. When the change feed generator 2152 posts events in the change feed, subscribing systems or applications can receive the change feed event. By generating a record of all changes that have happened, a system can stage data in different ways, and then replay the data back in whatever order the system wishes. This can include running the changes sequentially one by one and/or by jumping from one major change to the next. For example, to generate a graph at a particular time, all change feed events up to the particular time can be used to construct the graph.
The change feed can track the changes in each node in the graph and the relationships related to them, in some embodiments. If a user wants to subscribe to these changes and the user has proper access, the user can simply submit a web API call to have sequential notifications of each change that happens in the graph. A user and/or system can replay the changes one by one to reinstitute the graph at any given time slice. Even though the messages are “thin” and only include notification of change and the reference “id/seq id,” the change feed can keep a copy of every state of each node and/or relationship so that a user and/or system can retrieve those past states at any time for each node. Furthermore, a consumer of the change feed could also create dynamic “views” allowing different “snapshots” in time of what the graph looks like from a particular context. While the twin manager 2108 may contain the history and the current state of the graph based upon schema evaluation, a consumer can retain a copy of that data, and thereby create dynamic views using the change feed.
The schema and ontology 2154 can define the message schema and graph ontology of the twin manager 2108. The message schema can define what format messages received by the messaging manager 2140 should have, e.g., what parameters, what formats, etc. The ontology can define graph projections, e.g., the ontology that a user wishes to view. For example, various systems, applications, and/or users can be associated with a graph ontology. Accordingly, when the graph projection manager 2156 generates an graph projection for a user, system, or subscription, the graph projection manager 2156 can generate a graph projection according to the ontology specific to the user. For example, the ontology can define what types of entities are related in what order in a graph, for example, for the ontology for a subscription of “Customer A,” the graph projection manager 2156 can create relationships for a graph projection based on the rule:
For the ontology of a subscription of “Customer B,” the graph projection manager 156 can create relationships based on the rule:
The policy manager 2158 can be configured to respond to requests from other applications and/or systems for policies. The policy manager 2158 can consult a graph projection to determine what permissions different applications, users, and/or devices have. The graph projection can indicate various permissions that different types of entities have and the policy manager 2158 can search the graph projection to identify the permissions of a particular entity. The policy manager 2158 can facilitate fine grain access control with user permissions. The policy manager 2158 can apply permissions across a graph, e.g., if “user can view all data associated with floor 1” then they see all subsystem data for that floor, e.g., surveillance cameras, HVAC devices, fire detection and response devices, etc.
The twin manager 2108 includes a query manager 2165 and a twin function manager 2167. The query manger 2164 can be configured to handle queries received from a requesting system, e.g., the user device 2176, the applications 2110, and/or any other system. The query manager 2165 can receive queries that include query parameters and context. The query manager 2165 can query the graph projection database 2162 with the query parameters to retrieve a result. The query manager 2165 can then cause an event processor, e.g., a twin function, to operate based on the result and the context. In some embodiments, the query manager 2165 can select the twin function based on the context and/or perform operates based on the context.
The twin function manager 2167 can be configured to manage the execution of twin functions. The twin function manager 2167 can receive an indication of a context query that identifies a particular data element and/or pattern in the graph projection database 2162. Responsive to the particular data element and/or pattern occurring in the graph projection database 2162 (e.g., based on a new data event added to the graph projection database 2162 and/or change to nodes or edges of the graph projection database 2162, the twin function manager 2167 can cause a particular twin function to execute. The twin function can execute based on an event, context, and/or rules. The event can be data that the twin function executes against. The context can be information that provides a contextual description of the data, e.g., what device the event is associated with, what control point should be updated based on the event, etc.
Referring now to
The graph projection 2200 includes a device hub 2202 which may represent a software service that facilitates the communication of data and commands between the cloud platform 2106 and a device of the building subsystems 2122, e.g., door actuator 2214. The device hub 2202 is related to a connector 2204, an external system 2206, and a digital asset “Door Actuator” 2208 by edge 2250, edge 2252, and edge 2254.
The cloud platform 2106 can be configured to identify the device hub 2202, the connector 2204, the external system 2206 related to the door actuator 2214 by searching the graph projection 2200 and identifying the edges 22502-254 and edge 2258. The graph projection 2200 includes a digital representation of the “Door Actuator,” node 2208. The digital asset “Door Actuator” 2208 includes a “DeviceNameSpace” represented by node 2207 and related to the digital asset “Door Actuator” 2208 by the “Property of Object” edge 2256.
The “Door Actuator” 2214 has points and timeseries. The “Door Actuator” 2214 is related to “Point A” 2216 by a “has_a” edge 2260. The “Door Actuator” 2214 is related to “Point B” 2218 by a “has_A” edge 2258. Furthermore, timeseries associated with the points A and B are represented by nodes “TS” 2220 and “TS” 2222. The timeseries are related to the points A and B by “has_a” edge 2264 and “has_a” edge 2262. The timeseries “TS” 2220 has particular samples, sample 2210 and 2212 each related to “TS” 2220 with edges 2268 and 2266, respectively. Each sample includes a time and a value. Each sample may be an event received from the door actuator that the cloud platform 2106 ingests into the entity, relationship, and event database 2160, e.g., ingests into the graph projection 2200.
The graph projection 2200 includes a building 2234 representing a physical building. The building includes a floor represented by floor 2232 related to the building 2234 by the “has_a” edge from the building 2234 to the floor 2232. The floor has a space indicated by the edge “has a” 2270 between the floor 2232 and the space 2230. The space has particular capabilities, e.g., is a room that can be booked for a meeting, conference, private study time, etc. Furthermore, the booking can be canceled. The capabilities for the floor 2232 are represented by capabilities 2228 related to space 2230 by edge 2280. The capabilities 2228 are related to two different commands, command “book room” 2224 and command “cancel booking” 2226 related to capabilities 2228 by edge 2284 and edge 2282 respectively.
If the cloud platform 2106 receives a command to book the space represented by the node, space 2230, the cloud platform 2106 can search the graph projection 2200 for the capabilities 2228 related to the space 2230 to determine whether the cloud platform 2106 can book the room.
In some embodiments, the cloud platform 2106 could receive a request to book a room in a particular building, e.g., the building 2234. The cloud platform 2106 could search the graph projection 2200 to identify spaces that have the capabilities to be booked, e.g., identify the space 2230 based on the capabilities 2228 related to the space 2230. The cloud platform 2106 can reply to the request with an indication of the space and allow the requesting entity to book the space 2230.
The graph projection 2200 includes a policy 2236 for the floor 2232. The policy 2236 is related set for the floor 2232 based on a “To Floor” edge 2274 between the policy 2236 and the floor 2232. The policy 2236 is related to different roles for the floor 2232, read events 2238 via edge 2276 and send command 2240 via edge 2278. The policy 2236 is set for the entity 2203 based on has edge 2251 between the entity 2203 and the policy 2236.
The twin manager 2108 can identify policies for particular entities, e.g., users, software applications, systems, devices, etc. based on the policy 2236. For example, if the cloud platform 2106 receives a command to book the space 2230. The cloud platform 2106 can communicate with the twin manager 2108 to verify that the entity requesting to book the space 2230 has a policy to book the space. The twin manager 2108 can identify the entity requesting to book the space as the entity 2203 by searching the graph projection 2200. Furthermore, the twin manager 2108 can further identify the edge has 2251 between the entity 2203 and the policy 2236 and the edge 2278 between the policy 2236 and the command 2240.
Furthermore, the twin manager 2108 can identify that the entity 2203 has the ability to command the space 2230 based on the edge 2274 between the policy 2236 and the edge 2270 between the floor 2232 and the space 2230. In response to identifying the entity 2203 has the ability to book the space 2230, the twin manager 2108 can provide an indication to the cloud platform 2106.
Furthermore, if the entity makes a request to read events for the space 2230, e.g., the sample 2210 and the sample 2212, the twin manager 2108 can identify the edge has 2251 between the entity 2203 and the policy 2236, the edge 2278 between the policy 2236 and the read events 2238, the edge 2274 between the policy 2236 and the floor 2232, the “has_a” edge 2270 between the floor 2232 and the space 2230, the edge 2268 between the space 2230 and the door actuator 2214, the edge 2260 between the door actuator 2214 and the point A 2216, the “has a” edge 2264 between the point A 2216 and the TS 2220, and the edges 2268 and 2266 between the TS 2220 and the samples 2210 and 2212 respectively.
Referring now to
The connection broker 2354 is related to an agent that optimizes a space 2356 via edge 2398b. The agent represented by the node 2356 can book and cancel bookings for the space represented by the node 2230 based on the edge 2398b between the connection broker 2354 and the node 2356 and the edge 2398a between the capabilities 2228 and the connection broker 2354.
The connection broker 2354 is related to a cluster 2308 by edge 2398c. Cluster 2308 is related to connector B 2302 via edge 2398e and connector A 2306 via edge 2398d. The connector A 2306 is related to an external subscription service 2304. A connection broker 2310 is related to cluster 2308 via an edge 2311 representing a rest call that the connection broker represented by node 2310 can make to the cluster represented by cluster 2308.
The connection broker 2310 is related to a virtual meeting platform 2312 by an edge 2354. The node 2312 represents an external system that represents a virtual meeting platform. The connection broker represented by node 2310 can represent a software component that facilitates a connection between the cloud platform 2106 and the virtual meeting platform represented by node 2312. When the cloud platform 2106 needs to communicate with the virtual meeting platform represented by the node 2312, the cloud platform 2106 can identify the edge 2354 between the connection broker 2310 and the virtual meeting platform 2312 and select the connection broker represented by the node 2310 to facilitate communication with the virtual meeting platform represented by the node 2312.
A capabilities node 2318 can be connected to the connection broker 2310 via edge 2360. The capabilities 2318 can be capabilities of the virtual meeting platform represented by the node 2312 and can be related to the node 2312 through the edge 2360 to the connection broker 2310 and the edge 2354 between the connection broker 2310 and the node 2312. The capabilities 2318 can define capabilities of the virtual meeting platform represented by the node 2312. The node 2320 is related to capabilities 2318 via edge 2362. The capabilities may be an invite bob command represented by node 2316 and an email bob command represented by node 2314. The capabilities 2318 can be linked to a node 2320 representing a user, Bob. The cloud platform 2106 can facilitate email commands to send emails to the user Bob via the email service represented by the node 2304. The node 2304 is related to the connect a node 2306 via edge 2398f. Furthermore, the cloud platform 2106 can facilitate sending an invite for a virtual meeting via the virtual meeting platform represented by the node 2312 linked to the node 2318 via the edge 2358.
The node 2320 for the user Bob can be associated with the policy 2236 via the “has” edge 2364. Furthermore, the node 2320 can have a “check policy” edge 2366 with a portal node 2324. The device API node 2328 has a check policy edge 2370 to the policy node 2236. The portal node 2324 has an edge 2368 to the policy node 2236. The portal node 2324 has an edge 2323 to a node 2326 representing a user input manager (UIM). The portal node 2324 is related to the UIM node 2326 via an edge 2323. The UIM node 2326 has an edge 2323 to a device API node 2328. The UIM node 2326 is related to the door actuator node 2214 via edge 2372. The door actuator node 2214 has an edge 2374 to the device API node 2328. The door actuator 2214 has an edge 2335 to the connector virtual object 2334. The device hub 2332 is related to the connector virtual object via edge 2380. The device API node 2328 can be an API for the door actuator 2214. The connector virtual object 2334 is related to the device API node 2328 via the edge 2331.
The device API node 2328 is related to a transport connection broker 2330 via an edge 2329. The transport connection broker 2330 is related to a device hub 2332 via an edge 2378. The device hub represented by node 2332 can be a software component that hands the communication of data and commands for the door actuator 2214. The cloud platform 2106 can identify where to store data within the graph projection 2300 received from the door actuator by identifying the nodes and edges between the points 2216 and 2218 and the device hub node 2332. Similarly, the cloud platform 2308 can identify commands for the door actuator that can be facilitated by the device hub represented by the node 2332, e.g., by identifying edges between the device hub node 2332 and an open door node 2352 and an lock door node 2350. The door actuator 2214 has an edge “has mapped an asset” 2280 between the node 2214 and a capabilities node 2348. The capabilities node 2348 and the nodes 2352 and 2350 are linked by edges 2396 and 2394.
The device hub 2332 is linked to a cluster 2336 via an edge 2384. The cluster 2336 is linked to connector A 2340 and connector B 2338 by edges 2386 and the edge 2389. The connector A 2340 and the connector B 2338 is linked to an external system 2344 via edges 2388 and 2390. The external system 2344 is linked to a door actuator 2342 via an edge 2392.
Referring now to
A building node 2404 represents a particular building that includes two floors. A floor 1 node 2402 is linked to the building node 2404 via edge 2460 while a floor 2 node 2406 is linked to the building node 2404 via edge 2462. The floor 2 includes a particular room 2023 represented by edge 2464 between floor 2 node 2406 and room 2023 node 2408. Various pieces of equipment are included within the room 2023. A light represented by light node 2416, a bedside lamp node 2414, a bedside lamp node 2412, and a hallway light node 2410 are related to room 2023 node 2408 via edge 2466, edge 2472, edge 2470, and edge 2468.
The light represented by light node 2416 is related to a light connector 2426 via edge 2484. The light connector 2426 is related to multiple commands for the light represented by the light node 4216 via edges 2484, 2486, and 2488. The commands may be a brightness setpoint 2424, an on command 2425, and a hue setpoint 2428. The cloud platform 2106 can receive a request to identify commands for the light represented by the light node 2416 and can identify the nodes 2424-2428 and provide an indication of the commands represented by the nodes 2424-2428 to the requesting entity. The requesting entity can then send commands for the commands represented by the nodes 2424-2428.
The bedside lamp node 2414 is linked to a bedside lamp connector 2481 via an edge 2413. The connector 2481 is related to commands for the bedside lamp represented by the bedside lamp node 2414 via edges 2492, 2496, and 2494. The command nodes are a brightness setpoint node 2432, an on command node 2434, and a color command 2436. The hallway light 2410 is related to a hallway light connector 2446 via an edge 2498d. The hallway light connector 2446 is linked to multiple commands for the hallway light node 2410 via edges 2498g, 2498f, and 2498e. The commands are represented by an on command node 2452, a hue setpoint node 2450, and a light bulb activity node 2448.
The graph projection 2400 includes a name space node 2422 related to a server A node 2418 and a server B node 2420 via edges 2474 and 2476. The name space node 2422 is related to the bedside lamp connector 2481, the bedside lamp connector 2444, and the hallway light connector 2446 via edges 2482, 2480, and 2478. The bedside lamp connector 2444 is related to commands, e.g., the color command node 2440, the hue setpoint command 2438, a brightness setpoint command 2456, and an on command 2454 via edges 2498c, 2498b, 2498a, and 2498.
Referring now to
In the graph 2600 includes a tenant 2602. The tenant 2602 may represent an entity (e.g., user, company, etc.) that has a contract or agreement to use processing resources of the system 2100. The tenant 2602 includes two subscriptions, subscription 2604 and subscription 2606. The tenant 2602 is related to the subscription 2604 via edge 2628. The tenant 2602 is related to the subscription 2606 via the edge 2626. The tenant 2602 may be the owner of various stadiums, e.g., two stadiums. The subscription 2604 may be for a building stadium 2608. The subscription 2604 is related to the building stadium 2608 via the “hasPart” edge 2630. The building stadium 2608 is related to the subscription 2604 via the edge “isPartOf” 2632. The subscription 2606 can be for another building stadium, building stadium 2610. The subscription 2606 is related to the building stadium 2610 via an edge 2634.
The building stadium 2608 is related to the floor 2612. The building stadium 2608 is related to the floor 2612 via the “hasPart” edge 2636. The floor 2612 is related to the building stadium 2608 via the “isPartOf” edge 2638. The floor 2612 is related to the room 2614 via an “isLocatedIn” edge 2640. The room 2614 is related to the floor 2612 via the “hasLocation” edge 2642. The room 2614 is related to an asset 2616 via an edge 2646 while the asset 2616 is related to the room 2614 via an edge 2644.
The asset 2616 includes an event, the event 2618. The asset 2616 is related to the event 2618 via the edge 2648. The asset 2616 is related to the connector component 2620 via a “hasPart” edge 2652. The connector component 2620 is related to the asset 2616 via an “isPartOf” edge 2650. The connector component 2620 is related to the connector eventType 2622 via a “hasPoint” edge 2654 and is related to the connector command 2624 via a “hasPoint” edge 2656.
In some embodiments, responsive to the event 2618 being received and added to the building graph 2600, a twin function of a specific type can run and execute based at least in part on the event 2618. In some embodiments, the connector component 2620 can represent a stream of events where the event 2618 is one event of the stream. The twin manager 2108 can generate the connector component 2620 to represent the event stream, e.g., telemetry of the asset 2616. Additional events can be added to the building graph 2600 of the event stream and related via an edge to the connector component 2620. The event stream can be a virtual event stream generated based on other events. The connector component 2620 can represent a derived point for the virtual event stream. The event 2618 can include an identifier, “Associated_entity_ID” which may identify the asset, e.g., asset 2616, that the event 2618 is associated with.
The connector 2620 is related to a twin function type 2662 via an edge 2660. The twin function type 2662 can indicate a specific type of twin function that should execute based on the reception of the event 2618 and/or an event of the event stream with a particular event value. Furthermore, in some embodiments, the event 2618 can be an event generated by a twin function of the twin function of the twin function type 2662. The event 2618 can be added to the graph 2600 based on the twin function type 2662.
In some embodiments, the event 2618 represents a state of the asset 2616. Responsive to receiving the event 2618, a state of the asset 2616 can change, e.g., by the presence of the event 2618 in the graph 2600. In some embodiments, as a new event is received, the new event can be added to the building graph 2600 to replace the existing event 2618. In some embodiments, a twin function can execute responsive to a certain state of an asset changing in a particular manner.
The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements may be reversed or otherwise varied and the nature or number of discrete elements or positions may be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps may be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.
The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can include RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
Although the figures show a specific order of method steps, the order of the steps may differ from what is depicted. Also two or more steps may be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202221004267 | Jan 2022 | IN | national |
This application is a continuation-in-part of U.S. patent application Ser. No. 16/688,440, filed Nov. 19, 2019. This application also claims the benefit of and priority to Indian Provisional Patent Application No. 202221004267, filed Jan. 25, 2022. Both of these patent applications are incorporated herein by reference in their entireties.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16688440 | Nov 2019 | US |
| Child | 18101044 | US |
