Building management system with multi-module controller configuration interface
A unified interface for building management systems integrates programming and topology views, enabling efficient configuration by allowing direct editing of control logic and automatic topology updates, addressing the inefficiencies of conventional systems.
Patent Information
- Application Number
- PCT/CN2026/089848
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-07
- Filing Date
- 2026-04-10
- Publication Date
- 2026-11-12
AI Technical Summary
Conventional building management systems lack a unified interface that allows users to configure control logic and visualize network topology simultaneously, requiring manual updates and leading to inconsistent representations, thereby decreasing efficiency in implementing building management systems.
A unified user interface that integrates a programming view and a topology view within a single session, enabling users to edit control logic blocks directly and automatically update the topology view to reflect changes in module connections, improving efficiency by reducing the need for manual synchronization.
The integrated interface enhances the efficiency of configuring building management systems by allowing users to visualize and track controller module distribution and edge device connections, improving the understanding of relationships between control logic blocks and edge devices.
Smart Images

Figure PCTCN2026089848-FTAPPB-I100001 
Figure 00000060_0000 
Figure 00000061_0000
Abstract
Description
BUILDING MANAGEMENT SYSTEM WITH MULTI-MODULE CONTROLLER CONFIGURATION INTERFACECROSS-REFERENCE TO RELATED PATENT APPLICATIONS
[0001] This application claims the benefit of and priority to P. C. T. Patent Application No. PCT / CN2025 / 093178 filed May 7, 2025, and P.C.T. Patent Application No. PCT / CN2025 / 093181 filed May 7, 2025, both of which are incorporated by reference herein in their entireties.BACKGROUND
[0002] The present disclosure relates generally to building management systems. The present disclosure relates more particularly to user interfaces for tracking control module implementation across a building management network and programming control logic for edge devices.
[0003] A building management system (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 a heating, ventilation, or air conditioning (HVAC) system, a security system, a lighting system, a fire alerting system, another system that is capable of managing building functions or devices, or any combination thereof. BMS devices may be installed in any environment (e.g., an indoor area or an outdoor area) and the environment may include any number of buildings, spaces, zones, rooms, or areas. A BMS may include building controllers or other devices sold by Johnson Controls, Inc., as well as building devices and components from other sources.
[0004] A BMS may include one or more computer systems (e.g., servers, BMS controllers, etc. ) that serve as enterprise level controllers, application or data servers, head nodes, master controllers, or field controllers for the BMS. Such computer systems may communicate with multiple downstream building systems or subsystems (e.g., an HVAC system, a security system, etc. ) according to like or disparate protocols (e.g., LON, BACnet, etc. ) . The computer systems may also provide one or more human-machine interfaces or client interfaces (e.g., graphical user interfaces, reporting interfaces, text-based computer interfaces, client-facing web services, web servers that provide pages to web clients, etc. ) for controlling, viewing, or otherwise interacting with the BMS, its subsystems, and devices.SUMMARY
[0005] At least one aspect relates to an edge controller for a building management system. The edge controller includes one or more modules communicably coupled to one or more edge devices to implement an operational workflow for the one or more edge devices. The one or more modules include processing circuitry configured to generate, via a programming view, one or more control module nodes corresponding to the one or more modules of the edge controller, one or more node connections between the control module nodes indicative of modules of the edge controller being communicably coupled, and one or more control logic blocks to be executed by the modules of the edge controller. The control logic blocks include control logic for operation of the edge devices. The processing circuitry is configured to adjust, via the programming view, one or more operational parameters within the one or more control logic blocks to adjust the operational workflow for the edge devices. The processing circuitry is configured to generate a topology view of the modules of the edge controller by displaying one or more module blocks corresponding to the one or more control module nodes representative of the modules of the edge controller, where the one or more module blocks are connected by one or more module connections, and operate the one or more edge devices to adjust at least one condition within a building or campus using the operational workflow.
[0006] In some embodiments, the edge controller is configured to display the topology view and the programming view in a unified session on a user interface. In some embodiments, a first module block includes one or more IO connection points that correspond to one or more IO connection ports on a first edge device communicably coupled to the first module block. In some embodiments, the edge controller is configured to display, via the topology view, a number of connected input / output connection points for the first module block.
[0007] In some embodiments, the module blocks include a first module block and a second module block connected thereto by a first module connection, with the second module block downstream of the first module block. In some embodiments, the edge controller is configured to display the first module connection including a first connection indicator, where the first connection indicator indicates a first type of connection between the first module block and the second module block. In some embodiments, the first type of connection is an Ethernet connection or a serial communication connection. In some embodiments, the edge controller includes a plurality of Ethernet ports configured to communicate using TCP / IP communications.
[0008] In some embodiments, the edge controller is configured to automatically adjust the topology view, based on forming the control module nodes and the node connections therebetween in the programming view. In some embodiments, the edge controller is configured to generate, via the programming view, one or more control logic connections between the one or more control logic blocks to define the operational workflow for the one or more edge devices.
[0009] In some embodiments, the control logic blocks include one or more input / output parameters, and the programming view is configured to generate or adjust the one or more control logic connections between the input / output parameters of the control logic blocks. In some embodiments, the control logic blocks include one or more input / output parameters, with the one or more control logic connections form between the input / output parameters of the control logic blocks via user input on a user interface.
[0010] In some embodiments, a first control logic block includes one or more input / output parameters, and where the first control logic block is expandable within the user interface to adjust values for the one or more input / output parameters. In some embodiments, the edge controller is configured to automatically adjust a second control logic connection between blocks of the control logic blocks, based on forming a first control logic connection between the first control logic block and a second control logic block.
[0011] Another aspect relates to a method for implementing a building management system (BMS) . The method includes connecting one or more edge devices within the BMS via one or more modules of a controller, where the one or more modules are communicably coupled to the one or more edge devices to implement an operational workflow for the one or more edge devices. The method includes generating a user interface displaying a programming view including a plurality of control logic blocks including control logic to be executed by the modules of the controller, with the plurality of control logic blocks to define the operational workflow for the edge devices within the BMS. The method includes adjusting, via the programming view, one or more operational parameters within the one or more control logic blocks to adjust the operational workflow for the edge devices. The method includes generating a topology view of the modules of the controller, with the topology view including one or more module blocks communicably coupled to the modules of the controller, and where the module blocks are representative of the modules, where the one or more module blocks are connected by one or more module connections.
[0012] In some embodiments, the method further includes displaying a first module connection between a first module block and a second module block downstream of the first module block, with the first module connection including a first connection indicator indicating a first type of connection between the first module block and the second module block. In some embodiments, the method further includes displaying, via the topology view, a number of connected input / output points for the plurality of module blocks based on a number of connected input / output ports for edge devices connected to a first module of the controller.
[0013] In some embodiments, the programming view and the topology view are both generated in a unified session on the user interface. In some embodiments, the method further includes generating, via the programming view, one or more control module nodes corresponding to the modules of the controller, and one or more node connections between the control module nodes indicative of modules of the edge controller being communicably coupled. In some embodiments, the method further includes expanding a first control logic block of the plurality of control logic blocks, in the programming view, to display one or more input / output parameters for the first control logic block.
[0014] Another aspect relates to a building management system including one or more edge devices operably coupled to building equipment configured to adjust at least one condition within a building or campus, an edge controller including one or more modules communicably coupled to the one or more edge devices to implement an operational workflow for the one or more edge devices, and a user device communicably coupled to the edge devices and the edge controller, with the user device providing a user interface. The user device is configured to generate, via a programming view, one or more control module nodes corresponding to the one or more modules of the edge controller, one or more node connections between the control module nodes indicative of modules of the edge controller being communicably coupled, and one or more control logic blocks to be executed by the modules of the edge controller. The control logic blocks include control logic for operation of the edge devices. The user device is configured to adjust, via the programming view, one or more operational parameters within the one or more control logic blocks to adjust the operational workflow for the edge devices. The user device is configured to generate a topology view of the modules of the edge controller by displaying one or more module blocks corresponding to the one or more control module nodes representative of the modules of the edge controller, where the one or more module blocks are connected by one or more module connections, and operate the one or more edge devices to adjust at least one condition within a building or campus using the operational workflow.
[0015] These and other aspects and implementations are discussed in detail below. The foregoing information and the following detailed description include illustrative examples of various aspects and implementations and provide an overview or framework for understanding the nature and character of the claimed aspects and implementations. The drawings provide illustration and a further understanding of the various aspects and implementations and are incorporated in and constitute a part of this specification. Aspects can be combined, and it will be readily appreciated that features described in the context of one aspect of the invention can be combined with other aspects. Aspects can be implemented in any convenient form, for example, by appropriate computer programs, which may be carried on appropriate carrier media (computer readable media) , which may be tangible carrier media (e.g., disks) or intangible carrier media (e.g., communications signals) . Aspects may also be implemented using any suitable apparatus, which may take the form of programmable computers running computer programs arranged to implement the aspect. As used in the specification and in the claims, the singular form of ‘a, ’ ‘an, ’a nd ‘the’ include plural referents unless the context clearly dictates otherwise.BRIEF DESCRIPTION OF THE DRAWINGS
[0016] Various objects, aspects, features, and advantages of the disclosure will become more apparent and better understood by referring to the detailed description taken in conjunction with the accompanying drawings, in which like reference characters identify corresponding elements throughout. In the drawings, like reference numbers generally indicate identical, functionally similar, and / or structurally similar elements.
[0017] FIG. 1 is a drawing of a building equipped with a building management system (BMS) , according to some embodiments.
[0018] FIG. 2 is a block diagram of a BMS that serves the building of FIG. 1, according to some embodiments.
[0019] FIG. 3 is a block diagram of a BMS controller which can be used in the BMS of FIG. 2, according to some embodiments.
[0020] FIG. 4 is another block diagram of the BMS that serves the building of FIG. 1, according to some embodiments.
[0021] FIG. 5 is a block diagram of a BMS, according to some embodiments.
[0022] FIG. 6 is a diagram of a BMS including a user interface depicting a topology view of a controller and connected control modules, according to some embodiments.
[0023] FIG. 7 is a diagram of a BMS including a user interface to depict a topology view of a controller and connected control modules and a programming view to program the control modules of the controller, according to some embodiments.
[0024] FIG. 8A is a diagram of the BMS including the user interface depicting the topology view of a controller and connected control modules, according to some embodiments.
[0025] FIG. 8B is a diagram of the BMS including the user interface depicting a detail view within the topology view of one or said control modules, according to some embodiments.
[0026] FIG. 9 is a user interface within the BMS depicting a programming view for generating and / or adjusting control logic blocks for edge devices to be executed by the controller, according to some embodiments.
[0027] FIG. 10 is a user interface of a control logic block within the programming view for implementing operational workflow for edge devices to be executed by the controller, according to some embodiments.
[0028] FIGS 11A-11B are other user interfaces of control logic blocks within the programming view for implementing operational workflow for edge devices to be executed by the controller, according to some embodiments.
[0029] FIGS 12A-12B are other user interfaces of control logic blocks within the programming view for implementing operational workflow for edge devices to be executed by the controller, according to some embodiments.
[0030] FIG. 13 is a user interface within the BMS depicting the programming view for generating and / or adjusting control logic blocks for edge devices to be executed by the controller, according to some embodiments.
[0031] FIG. 14 is a user interface of connected control logic blocks within the programming view for implementing operational workflow for edge devices to be executed by the controller, according to some embodiments.
[0032] FIG. 15 is a flowchart for a method to implement a building management system, according to some embodiments.DETAILED DESCRIPTIONOverview
[0033] Building management systems can monitor and control building equipment to maintain environmental conditions within commercial, industrial, and / or residential facilities. Building management systems often include edge devices that interface with physical equipment and controllers that execute control logic to implement operational workflows. However, configuring and visualizing the network topology and control logic relationships between multiple controller modules and edge devices in building management systems remains challenging and leads to inefficient implementation of building management systems.
[0034] For example, controllers in building management systems can include multiple modules that can be communicably coupled to edge devices to coordinate operations across a network for said building management system. Users can configure control logic and module relationships within the building management system using various software tools. However, conventional building management systems can provide separate interfaces for programming control logic and for viewing network topology, such that users must navigate between disconnected tools to configure and understand the operational workflow of the building management system. And these systems don’ t automatically generate and / or update topology and / or programming views for display via the user interface based on adjustments made within the system, such as adding new controller modules, connecting new edge devices, and / or modifying control logic within the operational workflow. Instead, conventional systems require users to manually update topology views when module connections or control logic relationships change, resulting in inconsistent or outdated representations of the network, such that users cannot easily verify that the configured control logic corresponds to the physical or logical network structure. Furthermore and / or in addition to, conventional systems do not provide for a block-based programming view where control logic can be both visualized and adjusted within the programming view, which decreases the efficiency of programming within the building management system. Thereby, conventional approaches do not provide a unified interface that allows users to both configure control logic in a block-based programming view and visualize the module-level topology of the controller network in a single session on the user device.
[0035] The techniques described herein can provide a unified user interface that integrates a programming view and a topology view within a single session on user devices for implementation of building management systems. The techniques described herein improve the efficiency of these building management systems, as users can configure control logic blocks in a programming view and automatically generate a topology view of controller modules which implement the control logic. The programming view provides a block-based representation of control logic that can be edited directly in the programming view, and can automatically update the topology view to reflect changes in module connections. The topology view is automatically generated and / or updated to depict module blocks representative of the controller modules, such that the module blocks and connections therebetween provide a visual representation of the network topology. The user device can display the programming view and the topology view in a unified session, such that users can switch between the views without navigating to separate tools or interfaces, improving the efficiency of implementing the building management system via visualized tracking and programming interactions.
[0036] For example, and referring generally to the FIGURES, a building management system (BMS) may include one or more edge devices operably coupled to building equipment to adjust condition (s) within a building. The BMS may include an edge controller including one or more modules communicably coupled to the edge devices to implement an operational workflow for said edge devices. The BMS may include a user device providing a user interface to generate, via a programming view, one or more module blocks representing the modules of the controller and control logic blocks for the modules of the controller, the control logic blocks including control logic for connected edge devices, adjust, via the programming view, operational parameters within the control logic blocks to adjust the operational workflow, and automatically generate a topology view of the modules of the controller, with the topology view including the module blocks representative of the modules of the controller, where the module blocks are connected by module connections.
[0037] Thereby, the BMSs described herein can provide a user interface displaying a block-based programming view that allows users to edit control logic directly and visualize the operational workflow, and displaying a topology view to track controller module distribution and edge device connections across the BMS, such that users can understand the relationships between control logic blocks and edge devices, which improves the efficiency of configuring building management systems by reducing the need to manually synchronize programming and topology views, providing a technical improvement over conventional approaches. Building and Building Management System
[0038] Referring now to FIG. 1, a perspective view of a building 10 is shown, according to an exemplary embodiment. A BMS serves building 10. The BMS for building 10 may include any number or type of devices that serve building 10. For example, each floor may include one or more security devices, video surveillance cameras, fire detectors, smoke detectors, lighting systems, HVAC systems, or other building systems or devices. In modern BMSs, BMS devices can exist on different networks within the building (e.g., one or more wireless networks, one or more wired networks, etc. ) and yet serve the same building space or control loop. For example, BMS devices may be connected to different communications networks or field controllers even if the devices serve the same area (e.g., floor, conference room, building zone, tenant area, etc. ) or purpose (e.g., security, ventilation, cooling, heating, etc. ) .
[0039] BMS devices may collectively or individually be referred to as building equipment. Building equipment may include any number or type of BMS devices within or around building 10. For example, building equipment may include controllers, chillers, rooftop units, fire and security systems, elevator systems, thermostats, lighting, serviceable equipment (e.g., vending machines) , and / or any other type of equipment that can be used to control, automate, or otherwise contribute to an environment, state, or condition of building 10. The terms “BMS devices, ” “BMS device” and “building equipment” are used interchangeably throughout this disclosure.
[0040] Referring now to FIG. 2, a block diagram of a BMS 11 for building 10 is shown, according to an exemplary embodiment. BMS 11 is shown to include a plurality of BMS subsystems 20-26. Each BMS subsystem 20-26 is connected to a plurality of BMS devices and makes data points for varying connected devices available to upstream BMS controller 12. Additionally, BMS subsystems 20-26 may encompass other lower-level subsystems. For example, an HVAC system may be broken down further as “HVAC system A, ” “HVAC system B, ” etc. In some buildings, multiple HVAC systems or subsystems may exist in parallel and may not be a part of the same HVAC system 20.
[0041] As shown in FIG. 2, BMS 11 may include a HVAC system 20. HVAC system 20 may control HVAC operations building 10. HVAC system 20 is shown to include a lower-level HVAC system 42 (named “HVAC system A” ) . HVAC system 42 may control HVAC operations for a specific floor or zone of building 10. HVAC system 42 may be connected to air handling units (AHUs) 32, 34 (named “AHU A” and “AHU B, ” respectively, in BMS 11) . AHU 32 may serve variable air volume (VAV) boxes 38, 40 (named “VAV_3” and “VAV_4” in BMS 11) . Likewise, AHU 34 may serve VAV boxes 36 and 110 (named “VAV_2” and “VAV_1” ) . HVAC system 42 may also include chiller 30 (named “Chiller A” in BMS 11) . Chiller 30 may provide chilled fluid to AHU 32 and / or to AHU 34. HVAC system 42 may receive data (i.e., BMS inputs such as temperature sensor readings, damper positions, temperature setpoints, etc. ) from AHUs 32, 34. HVAC system 42 may provide such BMS inputs to HVAC system 20 and on to middleware 14 and BMS controller 12. Similarly, other BMS subsystems may receive inputs from other building devices or objects and provide the received inputs to BMS controller 12 (e.g., via middleware 14) .
[0042] Middleware 14 may include services that allow interoperable communication to, from, or between disparate BMS subsystems 20-26 of BMS 11 (e.g., HVAC systems from different manufacturers, HVAC systems that communicate according to different protocols, security / fire systems, IT resources, door access systems, etc. ) . Middleware 14 may be, for example, an EnNet server sold by Johnson Controls, Inc. While middleware 14 is shown as separate from BMS controller 12, middleware 14 and BMS controller 12 may integrated in some embodiments. For example, middleware 14 may be a part of BMS controller 12.
[0043] Still referring to FIG. 2, window control system 22 may receive shade control information from one or more shade controls, ambient light level information from one or more light sensors, and / or other BMS inputs (e.g., sensor information, setpoint information, current state information, etc. ) from downstream devices. Window control system 22 may include window controllers 107, 108 (e.g., named “local window controller A” and “local window controller B, ” respectively, in BMS 11) . Window controllers 107, 108 control the operation of subsets of window control system 22. For example, window controller 108 may control window blind or shade operations for a given room, floor, or building in the BMS.
[0044] Lighting system 24 may receive lighting related information from a plurality of downstream light controls (e.g., from room lighting 104) . Door access system 26 may receive lock control, motion, state, or other door related information from a plurality of downstream door controls. Door access system 26 is shown to include door access pad 106 (named “Door Access Pad 3F” ) , which may grant or deny access to a building space (e.g., a floor, a conference room, an office, etc. ) based on whether valid user credentials are scanned or entered (e.g., via a keypad, via a badge-scanning pad, etc. ) .
[0045] BMS subsystems 20-26 may be connected to BMS controller 12 via middleware 14 and may be configured to provide BMS controller 12 with BMS inputs from various BMS subsystems 20-26 and their varying downstream devices. BMS controller 12 may be configured to make differences in building subsystems transparent at the human-machine interface or client interface level (e.g., for connected or hosted user interface (UI) clients 16, remote applications 18, etc. ) . BMS controller 12 may be configured to describe or model different building devices and building subsystems using common or unified objects (e.g., software objects stored in memory) to help provide the transparency. Software equipment objects may allow developers to write applications capable of monitoring and / or controlling various types of building equipment regardless of equipment-specific variations (e.g., equipment model, equipment manufacturer, equipment version, etc. ) . Software building objects may allow developers to write applications capable of monitoring and / or controlling building zones on a zone-by-zone level regardless of the building subsystem makeup.
[0046] Referring now to FIG. 3, a block diagram illustrating a portion of BMS 11 in greater detail is shown, according to an exemplary embodiment. Particularly, FIG. 3 illustrates a portion of BMS 11 that services a conference room 102 of building 10 (named “B1_F3_CR5” ) . Conference room 102 may be affected by many different building devices connected to many different BMS subsystems. For example, conference room 102 includes or is otherwise affected by VAV box 110, window controller 108 (e.g., a blind controller) , a system of lights 104 (named “Room Lighting 17” ) , and a door access pad 106.
[0047] Each of the building devices shown at the top of FIG. 3 may include local control circuitry configured to provide signals to their supervisory controllers or more generally to the BMS subsystems 20-26. The local control circuitry of the building devices shown at the top of FIG. 3 may also be configured to receive and respond to control signals, commands, setpoints, or other data from their supervisory controllers. For example, the local control circuitry of VAV box 110 may include circuitry that affects an actuator in response to control signals received from a field controller that is a part of HVAC system 20. Window controller 108 may include circuitry that affects windows or blinds in response to control signals received from a field controller that is part of window control system (WCS) 22. Room lighting 104 may include circuitry that affects the lighting in response to control signals received from a field controller that is part of lighting system 24. Access pad 106 may include circuitry that affects door access (e.g., locking or unlocking the door) in response to control signals received from a field controller that is part of door access system 26.
[0048] Still referring to FIG. 3, BMS controller 12 is shown to include a BMS interface 132 in communication with middleware 14. In some embodiments, BMS interface 132 is a communications interface. For example, BMS interface 132 may include wired or wireless interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc. ) for conducting data communications with various systems, devices, or networks. BMS interface 132 can include an Ethernet card and port for sending and receiving data via an Ethernet-based communications network. In another example, BMS interface 132 includes a Wi-Fi transceiver for communicating via a wireless communications network. BMS interface 132 may be configured to communicate via local area networks or wide area networks (e.g., the Internet, a building WAN, etc. ) .
[0049] In some embodiments, BMS interface 132 and / or middleware 14 includes an application gateway configured to receive input from applications running on client devices. For example, BMS interface 132 and / or middleware 14 may include one or more wireless transceivers (e.g., a Wi-Fi transceiver, a Bluetooth transceiver, a NFC transceiver, a cellular transceiver, etc. ) for communicating with client devices. BMS interface 132 may be configured to receive building management inputs from middleware 14 or directly from one or more BMS subsystems 20-26. BMS interface 132 and / or middleware 14 can include any number of software buffers, queues, listeners, filters, translators, or other communications-supporting services.
[0050] Still referring to FIG. 3, BMS controller 12 is shown to include a processing circuit 134 including a processor 136 and memory 138. Processor 136 may be a general purpose or specific purpose processor, an application specific integrated circuit (ASIC) , one or more field programmable gate arrays (FPGAs) , a group of processing components, or other suitable processing components. Processor 136 is configured to execute computer code or instructions stored in memory 138 or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc. ) .
[0051] Memory 138 may 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. Memory 138 may 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. Memory 138 may 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. Memory 138 may be communicably connected to processor 136 via processing circuit 134 and may include computer code for executing (e.g., by processor 136) one or more processes described herein. When processor 136 executes instructions stored in memory 138 for completing the various activities described herein, processor 136 generally configures BMS controller 12 (and more particularly processing circuit 134) to complete such activities.
[0052] Still referring to FIG. 3, memory 138 is shown to include building objects 142. In some embodiments, BMS controller 12 uses building objects 142 to group otherwise ungrouped or unassociated devices so that the group may be addressed or handled by applications together and in a consistent manner (e.g., a single user interface for controlling all of the BMS devices that affect a particular building zone or room) . Building objects can apply to spaces of any granularity. For example, a building object can represent an entire building, a floor of a building, or individual rooms on each floor. In some embodiments, BMS controller 12 creates and / or stores a building object in memory 138 for each zone or room of building 10. Building objects 142 can be accessed by UI clients 16 and remote applications 18 to provide a comprehensive user interface for controlling and / or viewing information for a particular building zone. Building objects 142 may be created by building object creation module 152 and associated with equipment objects by object relationship module 158, described in greater detail below.
[0053] Still referring to FIG. 3, memory 138 is shown to include equipment definitions 140. Equipment definitions 140 stores the equipment definitions for various types of building equipment. Each equipment definition may apply to building equipment of a different type. For example, equipment definitions 140 may include different equipment definitions for variable air volume modular assemblies (VMAs) , fan coil units, air handling units (AHUs) , lighting fixtures, water pumps, and / or other types of building equipment.
[0054] Equipment definitions 140 define the types of data points that are generally associated with various types of building equipment. For example, an equipment definition for VMA may specify data point types such as room temperature, damper position, supply air flow, and / or other types data measured or used by the VMA. Equipment definitions 140 allow for the abstraction (e.g., generalization, normalization, broadening, etc. ) of equipment data from a specific BMS device so that the equipment data can be applied to a room or space.
[0055] Each of equipment definitions 140 may include one or more point definitions. Each point definition may define a data point of a particular type and may include search criteria for automatically discovering and / or identifying data points that satisfy the point definition. An equipment definition can be applied to multiple pieces of building equipment of the same general type (e.g., multiple different VMA controllers) . When an equipment definition is applied to a BMS device, the search criteria specified by the point definitions can be used to automatically identify data points provided by the BMS device that satisfy each point definition.
[0056] In some embodiments, equipment definitions 140 define data point types as generalized types of data without regard to the model, manufacturer, vendor, or other differences between building equipment of the same general type. The generalized data points defined by equipment definitions 140 allows each equipment definition to be referenced by or applied to multiple different variants of the same type of building equipment.
[0057] In some embodiments, equipment definitions 140 facilitate the presentation of data points in a consistent and user-friendly manner. For example, each equipment definition may define one or more data points that are displayed via a user interface. The displayed data points may be a subset of the data points defined by the equipment definition.
[0058] In some embodiments, equipment definitions 140 specify a system type (e.g., HVAC, lighting, security, fire, etc. ) , a system sub-type (e.g., terminal units, air handlers, central plants) , and / or data category (e.g., critical, diagnostic, operational) associated with the building equipment defined by each equipment definition. Specifying such attributes of building equipment at the equipment definition level allows the attributes to be applied to the building equipment along with the equipment definition when the building equipment is initially defined. Building equipment can be filtered by various attributes provided in the equipment definition to facilitate the reporting and management of equipment data from multiple building systems.
[0059] Equipment definitions 140 can be automatically created by abstracting the data points provided by archetypal controllers (e.g., typical or representative controllers) for various types of building equipment. In some embodiments, equipment definitions 140 are created by equipment definition module 154, described in greater detail below.
[0060] Still referring to FIG. 3, memory 138 is shown to include equipment objects 144. Equipment objects 144 may be software objects that define a mapping between a data point type (e.g., supply air temperature, room temperature, damper position) and an actual data point (e.g., a measured or calculated value for the corresponding data point type) for various pieces of building equipment. Equipment objects 144 may facilitate the presentation of equipment-specific data points in an intuitive and user-friendly manner by associating each data point with an attribute identifying the corresponding data point type. The mapping provided by equipment objects 144 may be used to associate a particular data value measured or calculated by BMS 11 with an attribute that can be displayed via a user interface.
[0061] Equipment objects 144 can be created (e.g., by equipment object creation module 156) by referencing equipment definitions 140. For example, an equipment object can be created by applying an equipment definition to the data points provided by a BMS device. The search criteria included in an equipment definition can be used to identify data points of the building equipment that satisfy the point definitions. A data point that satisfies a point definition can be mapped to an attribute of the equipment object corresponding to the point definition.
[0062] Each equipment object may include one or more attributes defined by the point definitions of the equipment definition used to create the equipment object. For example, an equipment definition which defines the attributes “Occupied Command, ” “Room Temperature, ” and “Damper Position” may result in an equipment object being created with the same attributes. The search criteria provided by the equipment definition are used to identify and map data points associated with a particular BMS device to the attributes of the equipment object. The creation of equipment objects is described in greater detail below with reference to equipment object creation module 156.
[0063] Equipment objects 144 may be related with each other and / or with building objects 142. Causal relationships can be established between equipment objects to link equipment objects to each other. For example, a causal relationship can be established between a VMA and an AHU which provides airflow to the VMA. Causal relationships can also be established between equipment objects 144 and building objects 142. For example, equipment objects 144 can be associated with building objects 142 representing particular rooms or zones to indicate that the equipment object serves that room or zone. Relationships between objects are described in greater detail below with reference to object relationship module 158.
[0064] Still referring to FIG. 3, memory 138 is shown to include client services 146 and application services 148. Client services 146 may be configured to facilitate interaction and / or communication between BMS controller 12 and various internal or external clients or applications. For example, client services 146 may include web services or application programming interfaces available for communication by UI clients 16 and remote applications 18 (e.g., applications running on a mobile device, energy monitoring applications, applications allowing a user to monitor the performance of the BMS, automated fault detection and diagnostics systems, etc. ) . Application services 148 may facilitate direct or indirect communications between remote applications 18, local applications 150, and BMS controller 12. For example, application services 148 may allow BMS controller 12 to communicate (e.g., over a communications network) with remote applications 18 running on mobile devices and / or with other BMS controllers.
[0065] In some embodiments, application services 148 facilitate an applications gateway for conducting electronic data communications with UI clients 16 and / or remote applications 18. For example, application services 148 may be configured to receive communications from mobile devices and / or BMS devices. Client services 146 may provide client devices with a graphical user interface that consumes data points and / or display data defined by equipment definitions 140 and mapped by equipment objects 144.
[0066] Still referring to FIG. 3, memory 138 is shown to include a building object creation module 152. Building object creation module 152 may be configured to create the building objects stored in building objects 142. Building object creation module 152 may create a software building object for various spaces within building 10. Building object creation module 152 can create a building object for a space of any size or granularity. For example, building object creation module 152 can create a building object representing an entire building, a floor of a building, or individual rooms on each floor. In some embodiments, building object creation module 152 creates and / or stores a building object in memory 138 for each zone or room of building 10.
[0067] The building objects created by building object creation module 152 can be accessed by UI clients 16 and remote applications 18 to provide a comprehensive user interface for controlling and / or viewing information for a particular building zone. Building objects 142 can group otherwise ungrouped or unassociated devices so that the group may be addressed or handled by applications together and in a consistent manner (e.g., a single user interface for controlling all of the BMS devices that affect a particular building zone or room) . In some embodiments, building object creation module 152 uses the systems and methods described in U.S. Patent App. No. 12 / 887,390, filed September 21, 2010, for creating software defined building objects.
[0068] In some embodiments, building object creation module 152 provides a user interface for guiding a user through a process of creating building objects. For example, building object creation module 152 may provide a user interface to client devices (e.g., via client services 146) that allows a new space to be defined. In some embodiments, building object creation module 152 defines spaces hierarchically. For example, the user interface for creating building objects may prompt a user to create a space for a building, for floors within the building, and / or for rooms or zones within each floor.
[0069] In some embodiments, building object creation module 152 creates building objects automatically or semi-automatically. For example, building object creation module 152 may automatically define and create building objects using data imported from another data source (e.g., user view folders, a table, a spreadsheet, etc. ) . In some embodiments, building object creation module 152 references an existing hierarchy for BMS 11 to define the spaces within building 10. For example, BMS 11 may provide a listing of controllers for building 10 (e.g., as part of a network of data points) that have the physical location (e.g., room name) of the controller in the name of the controller itself. Building object creation module 152 may extract room names from the names of BMS controllers defined in the network of data points and create building objects for each extracted room. Building objects may be stored in building objects 142.
[0070] Still referring to FIG. 3, memory 138 is shown to include an equipment definition module 154. Equipment definition module 154 may be configured to create equipment definitions for various types of building equipment and to store the equipment definitions in equipment definitions 140. In some embodiments, equipment definition module 154 creates equipment definitions by abstracting the data points provided by archetypal controllers (e.g., typical or representative controllers) for various types of building equipment. For example, equipment definition module 154 may receive a user selection of an archetypal controller via a user interface. The archetypal controller may be specified as a user input or selected automatically by equipment definition module 154. In some embodiments, equipment definition module 154 selects an archetypal controller for building equipment associated with a terminal unit such as a VMA.
[0071] Equipment definition module 154 may identify one or more data points associated with the archetypal controller. Identifying one or more data points associated with the archetypal controller may include accessing a network of data points provided by BMS 11. The network of data points may be a hierarchical representation of data points that are measured, calculated, or otherwise obtained by various BMS devices. BMS devices may be represented in the network of data points as nodes of the hierarchical representation with associated data points depending from each BMS device. Equipment definition module 154 may find the node corresponding to the archetypal controller in the network of data points and identify one or more data points which depend from the archetypal controller node.
[0072] Equipment definition module 154 may generate a point definition for each identified data point of the archetypal controller. Each point definition may include an abstraction of the corresponding data point that is applicable to multiple different controllers for the same type of building equipment. For example, an archetypal controller for a particular VMA (i.e., “VMA-20” ) may be associated an equipment-specific data point such as “VMA-20. DPR-POS” (i.e., the damper position of VMA-20) and / or “VMA-20. SUP-FLOW” (i.e., the supply air flow rate through VMA-20) . Equipment definition module 154 abstract the equipment-specific data points to generate abstracted data point types that are generally applicable to other equipment of the same type. For example, equipment definition module 154 may abstract the equipment-specific data point “VMA-20. DPR-POS” to generate the abstracted data point type “DPR-POS” and may abstract the equipment-specific data point “VMA-20. SUP-FLOW” to generate the abstracted data point type “SUP-FLOW. ” Advantageously, the abstracted data point types generated by equipment definition module 154 can be applied to multiple different variants of the same type of building equipment (e.g., VMAs from different manufacturers, VMAs having different models or output data formats, etc. ) .
[0073] In some embodiments, equipment definition module 154 generates a user-friendly label for each point definition. The user-friendly label may be a plain text description of the variable defined by the point definition. For example, equipment definition module 154 may generate the label “Supply Air Flow” for the point definition corresponding to the abstracted data point type “SUP-FLOW” to indicate that the data point represents a supply air flow rate through the VMA. The labels generated by equipment definition module 154 may be displayed in conjunction with data values from BMS devices as part of a user-friendly interface.
[0074] In some embodiments, equipment definition module 154 generates search criteria for each point definition. The search criteria may include one or more parameters for identifying another data point (e.g., a data point associated with another controller of BMS 11 for the same type of building equipment) that represents the same variable as the point definition. Search criteria may include, for example, an instance number of the data point, a network address of the data point, and / or a network point type of the data point.
[0075] In some embodiments, search criteria include a text string abstracted from a data point associated with the archetypal controller. For example, equipment definition module 154 may generate the abstracted text string “SUP-FLOW” from the equipment-specific data point “VMA-20. SUP-FLOW. ” Advantageously, the abstracted text string matches other equipment-specific data points corresponding to the supply air flow rates of other BMS devices (e.g., “VMA-18. SUP-FLOW, ” “SUP-FLOW. VMA-01, ” etc. ) . Equipment definition module 154 may store a name, label, and / or search criteria for each point definition in memory 138.
[0076] Equipment definition module 154 may use the generated point definitions to create an equipment definition for a particular type of building equipment (e.g., the same type of building equipment associated with the archetypal controller) . The equipment definition may include one or more of the generated point definitions. Each point definition defines a potential attribute of BMS devices of the particular type and provides search criteria for identifying the attribute among other data points provided by such BMS devices.
[0077] In some embodiments, the equipment definition created by equipment definition module 154 includes an indication of display data for BMS devices that reference the equipment definition. Display data may define one or more data points of the BMS device that will be displayed via a user interface. In some embodiments, display data are user defined. For example, equipment definition module 154 may prompt a user to select one or more of the point definitions included in the equipment definition to be represented in the display data. Display data may include the user-friendly label (e.g., “Damper Position” ) and / or short name (e.g., “DPR-POS” ) associated with the selected point definitions.
[0078] In some embodiments, equipment definition module 154 provides a visualization of the equipment definition via a graphical user interface. The visualization of the equipment definition may include a point definition portion which displays the generated point definitions, a user input portion configured to receive a user selection of one or more of the point definitions displayed in the point definition portion, and / or a display data portion which includes an indication of an abstracted data point corresponding to each of the point definitions selected via the user input portion. The visualization of the equipment definition can be used to add, remove, or change point definitions and / or display data associated with the equipment definitions.
[0079] Equipment definition module 154 may generate an equipment definition for each different type of building equipment in BMS 11 (e.g., VMAs, chillers, AHUs, etc. ) . Equipment definition module 154 may store the equipment definitions in a data storage device (e.g., memory 138, equipment definitions 140, an external or remote data storage device, etc. ) .
[0080] Still referring to FIG. 3, memory 138 is shown to include an equipment object creation module 156. Equipment object creation module 156 may be configured to create equipment objects for various BMS devices. In some embodiments, equipment object creation module 156 creates an equipment object by applying an equipment definition to the data points provided by a BMS device. For example, equipment object creation module 156 may receive an equipment definition created by equipment definition module 154. Receiving an equipment definition may include loading or retrieving the equipment definition from a data storage device.
[0081] In some embodiments, equipment object creation module 156 determines which of a plurality of equipment definitions to retrieve based on the type of BMS device used to create the equipment object. For example, if the BMS device is a VMA, equipment object creation module 156 may retrieve the equipment definition for VMAs; whereas if the BMS device is a chiller, equipment object creation module 156 may retrieve the equipment definition for chillers. The type of BMS device to which an equipment definition applies may be stored as an attribute of the equipment definition. Equipment object creation module 156 may identify the type of BMS device being used to create the equipment object and retrieve the corresponding equipment definition from the data storage device.
[0082] In other embodiments, equipment object creation module 156 receives an equipment definition prior to selecting a BMS device. Equipment object creation module 156 may identify a BMS device of BMS 11 to which the equipment definition applies. For example, equipment object creation module 156 may identify a BMS device that is of the same type of building equipment as the archetypal BMS device used to generate the equipment definition. In various embodiments, the BMS device used to generate the equipment object may be selected automatically (e.g., by equipment object creation module 156) , manually (e.g., by a user) or semi-automatically (e.g., by a user in response to an automated prompt from equipment object creation module 156) .
[0083] In some embodiments, equipment object creation module 156 creates an equipment discovery table based on the equipment definition. For example, equipment object creation module 156 may create an equipment discovery table having attributes (e.g., columns) corresponding to the variables defined by the equipment definition (e.g., a damper position attribute, a supply air flow rate attribute, etc. ) . Each column of the equipment discovery table may correspond to a point definition of the equipment definition. The equipment discovery table may have columns that are categorically defined (e.g., representing defined variables) but not yet mapped to any particular data points.
[0084] Equipment object creation module 156 may use the equipment definition to automatically identify one or more data points of the selected BMS device to map to the columns of the equipment discovery table. Equipment object creation module 156 may search for data points of the BMS device that satisfy one or more of the point definitions included in the equipment definition. In some embodiments, equipment object creation module 156 extracts a search criterion from each point definition of the equipment definition. Equipment object creation module 156 may access a data point network of the building automation system to identify one or more data points associated with the selected BMS device. Equipment object creation module 156 may use the extracted search criterion to determine which of the identified data points satisfy one or more of the point definitions.
[0085] In some embodiments, equipment object creation module 156 automatically maps (e.g., links, associates, relates, etc. ) the identified data points of selected BMS device to the equipment discovery table. A data point of the selected BMS device may be mapped to a column of the equipment discovery table in response to a determination by equipment object creation module 156 that the data point satisfies the point definition (e.g., the search criteria) used to generate the column. For example, if a data point of the selected BMS device has the name “VMA-18. SUP-FLOW” and a search criterion is the text string “SUP-FLOW, ” equipment object creation module 156 may determine that the search criterion is met. Accordingly, equipment object creation module 156 may map the data point of the selected BMS device to the corresponding column of the equipment discovery table.
[0086] Advantageously, equipment object creation module 156 may create multiple equipment objects and map data points to attributes of the created equipment objects in an automated fashion (e.g., without human intervention, with minimal human intervention, etc. ) . The search criteria provided by the equipment definition facilitates the automatic discovery and identification of data points for a plurality of equipment object attributes. Equipment object creation module 156 may label each attribute of the created equipment objects with a device-independent label derived from the equipment definition used to create the equipment object. The equipment objects created by equipment object creation module 156 can be viewed (e.g., via a user interface) and / or interpreted by data consumers in a consistent and intuitive manner regardless of device-specific differences between BMS devices of the same general type. The equipment objects created by equipment object creation module 156 may be stored in equipment objects 144.
[0087] Still referring to FIG. 3, memory 138 is shown to include an object relationship module 158. Object relationship module 158 may be configured to establish relationships between equipment objects 144. In some embodiments, object relationship module 158 establishes causal relationships between equipment objects 144 based on the ability of one BMS device to affect another BMS device. For example, object relationship module 158 may establish a causal relationship between a terminal unit (e.g., a VMA) and an upstream unit (e.g., an AHU, a chiller, etc. ) which affects an input provided to the terminal unit (e.g., air flow rate, air temperature, etc. ) .
[0088] Object relationship module 158 may establish relationships between equipment objects 144 and building objects 142 (e.g., spaces) . For example, object relationship module 158 may associate equipment objects 144 with building objects 142 representing particular rooms or zones to indicate that the equipment object serves that room or zone. In some embodiments, object relationship module 158 provides a user interface through which a user can define relationships between equipment objects 144 and building objects 142. For example, a user can assign relationships in a “drag and drop” fashion by dragging and dropping a building object and / or an equipment object into a “serving” cell of an equipment object provided via the user interface to indicate that the BMS device represented by the equipment object serves a particular space or BMS device.
[0089] Still referring to FIG. 3, memory 138 is shown to include a building control services module 160. Building control services module 160 may be configured to automatically control BMS 11 and the various subsystems thereof. Building control services module 160 may utilize closed loop control, feedback control, PI control, model predictive control, or any other type of automated building control methodology to control the environment (e.g., a variable state or condition) within building 10.
[0090] Building control services module 160 may receive inputs from sensory devices (e.g., temperature sensors, pressure sensors, flow rate sensors, humidity sensors, electric current sensors, cameras, radio frequency sensors, microphones, etc. ) , user input devices (e.g., computer terminals, client devices, user devices, etc. ) or other data input devices via BMS interface 132. Building control services module 160 may apply the various inputs to a building energy use model and / or a control algorithm to determine an output for one or more building control devices (e.g., dampers, air handling units, chillers, boilers, fans, pumps, etc. ) in order to affect a variable state or condition within building 10 (e.g., zone temperature, humidity, air flow rate, etc. ) .
[0091] In some embodiments, building control services module 160 is configured to control the environment of building 10 on a zone-individualized level. For example, building control services module 160 may control the environment of two or more different building zones using different setpoints, different constraints, different control methodology, and / or different control parameters. Building control services module 160 may operate BMS 11 to maintain building conditions (e.g., temperature, humidity, air quality, etc. ) within a setpoint range, to optimize energy performance (e.g., to minimize energy consumption, to minimize energy cost, etc. ) , and / or to satisfy any constraint or combination of constraints as may be desirable for various implementations.
[0092] In some embodiments, building control services module 160 uses the location of various BMS devices to translate an input received from a building system into an output or control signal for the building system. Building control services module 160 may receive location information for BMS devices and automatically set or recommend control parameters for the BMS devices based on the locations of the BMS devices. For example, building control services module 160 may automatically set a flow rate setpoint for a VAV box based on the size of the building zone in which the VAV box is located.
[0093] Building control services module 160 may determine which of a plurality of sensors to use in conjunction with a feedback control loop based on the locations of the sensors within building 10. For example, building control services module 160 may use a signal from a temperature sensor located in a building zone as a feedback signal for controlling the temperature of the building zone in which the temperature sensor is located.
[0094] In some embodiments, building control services module 160 automatically generates control algorithms for a controller or a building zone based on the location of the zone in the building 10. For example, building control services module 160 may be configured to predict a change in demand resulting from sunlight entering through windows based on the orientation of the building and the locations of the building zones (e.g., east-facing, west-facing, perimeter zones, interior zones, etc. ) .
[0095] Building control services module 160 may use zone location information and interactions between adjacent building zones (rather than considering each zone as an isolated system) to more efficiently control the temperature and / or airflow within building 10. For control loops that are conducted at a larger scale (i.e., floor level) building control services module 160 may use the location of each building zone and / or BMS device to coordinate control functionality between building zones. For example, building control services module 160 may consider heat exchange and / or air exchange between adjacent building zones as a factor in determining an output control signal for the building zones.
[0096] In some embodiments, building control services module 160 is configured to optimize the energy efficiency of building 10 using the locations of various BMS devices and the control parameters associated therewith. Building control services module 160 may be configured to achieve control setpoints using building equipment with a relatively lower energy cost (e.g., by causing airflow between connected building zones) in order to reduce the loading on building equipment with a relatively higher energy cost (e.g., chillers and roof top units) . For example, building control services module 160 may be configured to move warmer air from higher elevation zones to lower elevation zones by establishing pressure gradients between connected building zones.
[0097] Referring now to FIG. 4, another block diagram illustrating a portion of BMS 11 in greater detail is shown, according to some embodiments. BMS 11 can be implemented in building 10 to automatically monitor and control various building functions. BMS 11 is shown to include BMS controller 12 and a plurality of building subsystems 428. Building subsystems 428 are shown to include a building electrical subsystem 434, an information communication technology (ICT) subsystem 436, a security subsystem 438, a HVAC subsystem 440, a lighting subsystem 442, a lift / escalators subsystem 432, and a fire safety subsystem 430. In various embodiments, building subsystems 428 can include fewer, additional, or alternative subsystems. For example, building subsystems 428 may 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 building 10.
[0098] Each of building subsystems 428 can include any number of devices, controllers, and connections for completing its individual functions and control activities. HVAC subsystem 440 can include many of the same components as HVAC system 20, as described with reference to FIGS. 2-3. For example, HVAC subsystem 440 can include 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 building 10. Lighting subsystem 442 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 438 can include occupancy sensors, video surveillance cameras, digital video recorders, video processing servers, intrusion detection devices, access control devices and servers, or other security-related devices.
[0099] Still referring to FIG. 4, BMS controller 12 is shown to include a communications interface 407 and a BMS interface 132. Interface 407 may facilitate communications between BMS controller 12 and external applications (e.g., monitoring and reporting applications 422, enterprise control applications 426, remote systems and applications 444, applications residing on client devices 448, etc. ) for allowing user control, monitoring, and adjustment to BMS controller 12 and / or subsystems 428. Interface 407 may also facilitate communications between BMS controller 12 and client devices 448. BMS interface 132 may facilitate communications between BMS controller 12 and building subsystems 428 (e.g., HVAC, lighting security, lifts, power distribution, business, etc. ) .
[0100] Interfaces 407, 132 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 428 or other external systems or devices. In various embodiments, communications via interfaces 407, 132 can be direct (e.g., local wired or wireless communications) or via a communications network 446 (e.g., a WAN, the Internet, a cellular network, etc. ) . For example, interfaces 407, 132 can include an Ethernet card and port for sending and receiving data via an Ethernet-based communications link or network. In another example, interfaces 407, 132 can include a Wi-Fi transceiver for communicating via a wireless communications network. In another example, one or both of interfaces 407, 132 can include cellular or mobile phone communications transceivers. In one embodiment, communications interface 407 is a power line communications interface and BMS interface 132 is an Ethernet interface. In other embodiments, both communications interface 407 and BMS interface 132 are Ethernet interfaces or are the same Ethernet interface.
[0101] Still referring to FIG. 4, BMS controller 12 is shown to include a processing circuit 134 including a processor 136 and memory 138. Processing circuit 134 can be communicably connected to BMS interface 132 and / or communications interface 407 such that processing circuit 134 and the various components thereof can send and receive data via interfaces 407, 132. Processor 136 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.
[0102] Memory 138 (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 138 can be or include volatile memory or non-volatile memory. Memory 138 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 some embodiments, memory 138 is communicably connected to processor 136 via processing circuit 134 and includes computer code for executing (e.g., by processing circuit 134 and / or processor 136) one or more processes described herein.
[0103] In some embodiments, BMS controller 12 is implemented within a single computer (e.g., one server, one housing, etc. ) . In various other embodiments BMS controller 12 can be distributed across multiple servers or computers (e.g., that can exist in distributed locations) . Further, while FIG. 4 shows applications 422 and 426 as existing outside of BMS controller 12, in some embodiments, applications 422 and 426 can be hosted within BMS controller 12 (e.g., within memory 138) .
[0104] Still referring to FIG. 4, memory 138 is shown to include an enterprise integration layer 410, an automated measurement and validation (AM&V) layer 412, a demand response (DR) layer 414, a fault detection and diagnostics (FDD) layer 416, an integrated control layer 418, and a building subsystem integration later 420. Layers 410-420 can be configured to receive inputs from building subsystems 428 and other data sources, determine optimal control actions for building subsystems 428 based on the inputs, generate control signals based on the optimal control actions, and provide the generated control signals to building subsystems 428. The following paragraphs describe some of the general functions performed by each of layers 410-420 in BMS 11.
[0105] Enterprise integration layer 410 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 426 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 426 may also or alternatively be configured to provide configuration GUIs for configuring BMS controller 12. In yet other embodiments, enterprise control applications 426 can work with layers 410-420 to optimize building performance (e.g., efficiency, energy use, comfort, or safety) based on inputs received at interface 407 and / or BMS interface 132.
[0106] Building subsystem integration layer 420 can be configured to manage communications between BMS controller 12 and building subsystems 428. For example, building subsystem integration layer 420 may receive sensor data and input signals from building subsystems 428 and provide output data and control signals to building subsystems 428. Building subsystem integration layer 420 may also be configured to manage communications between building subsystems 428. Building subsystem integration layer 420 translate communications (e.g., sensor data, input signals, output signals, etc. ) across a plurality of multi-vendor / multi-protocol systems.
[0107] Demand response layer 414 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 building 10. 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 424, from energy storage 427, or from other sources. Demand response layer 414 may receive inputs from other layers of BMS controller 12 (e.g., building subsystem integration layer 420, integrated control layer 418, 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 may 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.
[0108] According to some embodiments, demand response layer 414 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 418, changing control strategies, changing setpoints, or activating / deactivating building equipment or subsystems in a controlled manner. Demand response layer 414 may also include control logic configured to determine when to utilize stored energy. For example, demand response layer 414 may determine to begin using energy from energy storage 427 just prior to the beginning of a peak use hour.
[0109] In some embodiments, demand response layer 414 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 414 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 may represent collections of building equipment (e.g., subplants, chiller arrays, etc. ) or individual devices (e.g., individual chillers, heaters, pumps, etc. ) .
[0110] Demand response layer 414 may 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 setpoint before returning to a normally scheduled setpoint, 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. ) .
[0111] Integrated control layer 418 can be configured to use the data input or output of building subsystem integration layer 420 and / or demand response later 414 to make control decisions. Due to the subsystem integration provided by building subsystem integration layer 420, integrated control layer 418 can integrate control activities of the subsystems 428 such that the subsystems 428 behave as a single integrated supersystem. In some embodiments, integrated control layer 418 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 418 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 420.
[0112] Integrated control layer 418 is shown to be logically below demand response layer 414. Integrated control layer 418 can be configured to enhance the effectiveness of demand response layer 414 by enabling building subsystems 428 and their respective control loops to be controlled in coordination with demand response layer 414. This configuration may advantageously reduce disruptive demand response behavior relative to conventional systems. For example, integrated control layer 418 can be configured to assure that a demand response-driven upward adjustment to the setpoint 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.
[0113] Integrated control layer 418 can be configured to provide feedback to demand response layer 414 so that demand response layer 414 checks that constraints (e.g., temperature, lighting levels, etc. ) are properly maintained even while demanded load shedding is in progress. The constraints may also include setpoint or sensed boundaries relating to safety, equipment operating limits and performance, comfort, fire codes, electrical codes, energy codes, and the like. Integrated control layer 418 is also logically below fault detection and diagnostics layer 416 and automated measurement and validation layer 412. Integrated control layer 418 can be configured to provide calculated inputs (e.g., aggregations) to these higher levels based on outputs from more than one building subsystem.
[0114] Automated measurement and validation (AM&V) layer 412 can be configured to verify that control strategies commanded by integrated control layer 418 or demand response layer 414 are working properly (e.g., using data aggregated by AM&V layer 412, integrated control layer 418, building subsystem integration layer 420, FDD layer 416, or otherwise) . The calculations made by AM&V layer 412 can be based on building system energy models and / or equipment models for individual BMS devices or subsystems. For example, AM&V layer 412 may compare a model-predicted output with an actual output from building subsystems 428 to determine an accuracy of the model.
[0115] Fault detection and diagnostics (FDD) layer 416 can be configured to provide on-going fault detection for building subsystems 428, building subsystem devices (i.e., building equipment) , and control algorithms used by demand response layer 414 and integrated control layer 418. FDD layer 416 may receive data inputs from integrated control layer 418, directly from one or more building subsystems or devices, or from another data source. FDD layer 416 may 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.
[0116] FDD layer 416 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 420. In other exemplary embodiments, FDD layer 416 is configured to provide “fault” events to integrated control layer 418 which executes control strategies and policies in response to the received fault events. According to some embodiments, FDD layer 416 (or a policy executed by an integrated control engine or business rules engine) may shut-down systems or direct control activities around faulty devices or systems to reduce energy waste, extend equipment life, or assure proper control response.
[0117] FDD layer 416 can be configured to store or access a variety of different system data stores (or data points for live data) . FDD layer 416 may 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 428 may generate temporal (i.e., time-series) data indicating the performance of BMS 11 and the various components thereof. The data generated by building subsystems 428 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 setpoint. These processes can be examined by FDD layer 416 to expose when the system begins to degrade in performance and alert a user to repair the fault before it becomes more severe. User Interface with Automated Topology View and Block-Based Programming View
[0118] Referring to FIGS 5-14, a building management system (BMS) 500 may include one or more edge devices 502 operably coupled to building equipment configured to adjust at least one condition within a building (e.g., building 10, and / or a campus, etc. ) . The BMS 500 may be any type of networked control system that includes controllers, edge devices, and / or user interfaces for monitoring and controlling building equipment. For example, the BMS 500 may be similar to and / or include one or more components of the BMS 11, as described herein. In some embodiments, a controller 510 (e.g., an edge controller, and / or a controller similar to the BMS controller 12, etc. ) may include one or more control modules 511 (e.g., one or more control units, such as a primary controller and / or one or more secondary controllers coupled thereto, such as one or more input / output control units, etc. ) to execute control logic in an operational workflow for the edge devices 502 within the BMS 500.
[0119] The control modules 511 of the controller 510 may be physical and / or logical modules of the controller 510 that include processing circuitry, memory, communication interfaces, and / or input / output ports configured to execute control logic and interface with at least some of the edge devices 502. For example, in some embodiments, the control modules 511 may be implemented as separate hardware modules mounted in distinct enclosures and / or rack positions within a building or facility, with the hardware modules including a dedicated processor, non-volatile memory, and / or communication circuitry to execute control operations independently of other control modules 511. In some embodiments, the control modules 511 may be implemented as virtual modules executing as separate software processes, containers, and / or virtual machine instances on shared computing hardware within the controller 510, where the virtual modules allocated a portion of processing resources, memory, and / or communication bandwidth to execute control logic for a designated subset of the edge devices 502. The control modules 511 may be independently configured and / or connected to form a distributed control system within the BMS 500, where the control modules 511 include one or more module identifiers (e.g., a unique identifier, such as a network address, a device identifier, etc., and / or one or more types of communication channels or parameters, etc. ) that define how the control modules 511 exchange data with other control modules and / or the edge devices 502.
[0120] In some embodiments, the controller 510 may provide a user interface 505 for user interaction (e.g., engagement, analysis, programming, viewing, etc. ) with the BMS 500. For example, the BMS 500 may include a user device 504 (e.g., UI clients 16, remote applications 18, remote applications 444, client devices 448, etc., as described herein) displaying the user interface 505. For example, in some embodiments, the controller 510 may provide (e.g., transmit, export, display, etc. ) the user interface 505 as an application (e.g., software program, etc. ) that is operable (e.g., executed, runs, etc. ) on the user device 504. For another example, in some embodiments, the controller 510 may provide the user interface 505 via a web interface (e.g., where the web interface may be accessible via the user device 504, etc. ) . The user interface 505 provides for a unified session for visualizing programming views and / or topology views with the BMS 500. For example, BMS users may edit control logic directly in a block format within a programming view 506. In some embodiments, the controller 510 may be the user device 504. In some embodiments, the controller 510 may implement and / or provide the user interface 505 via the operations described herein. In some embodiments, the user device 504 may implement and / or provide the user interface 505 via the operations described herein.
[0121] The controller 510 executes control logic blocks that are adjustable within the programming view 506 to at least partially define an operational workflow for the edge devices 502. In some embodiments, BMS users may be provided with a hierarchical visual of controllers and / or controller modules within the BMS 500 (e.g., the network thereof, etc. ) via a topology view 508. The BMS 500 generates the topology view 508 to display one or more control module blocks 512 (e.g., controller module blocks, etc. ) of the controller 510 of the BMS 500 and / or one or more module connections 520 therebetween, based on one or more control module nodes 518 and / or one or more node connections 519 (e.g., control module node connections, etc. ) .
[0122] The control module nodes 518 may be representative of the control modules 511 of the controller 510. For example, the control module nodes 518 may be generated within the programming view 506 to define the structure of the controller 510 and / or the control modules 511 thereof within the BMS 500. The one or more control module nodes 518 may be displayed in a designated panel within the user interface 505, shown as the network tree panel 517 (e.g., a list view and / or a hierarchical tree within the user interface 505, such as shown in FIGS 6 and 9, etc. ) , where the topology view 508 displays the control module blocks 512 corresponding to the one or more control module nodes 518 to visually represent the control modules 511 of the controller 510 deployed throughout the BMS 500. The node connections 519 between the control module nodes 518 may be indicative of at least some of the control modules 511 of the controller 510 being communicably coupled (e.g., indicating that two or more control modules 511 are communicably coupled to each other, etc. ) . In some embodiments, the topology view 508 may be generated based on the one or more control module nodes 518 and the node connections 519 established in the programming view 506, such that the topology view 508 reflects the current configuration of the BMS 500.
[0123] In some embodiments, the user device 504 may be one or more computing devices that includes one or more processors communicably coupled to memory (e.g., where the processors execute readable instructions and / or algorithms stored in the memory, etc. ) . The user device 504 is configured to present the user interface 505 and / or communicate with the controller 510 and / or the edge devices 502 within the BMS 500. For example, the user device 504 may be and / or include a desktop computer, a laptop, a tablet, a smartphone, or any other computing device capable of executing software applications and displaying graphical user interfaces. In some embodiments, the user interface 505 may be any type of graphical user interface that includes interactive elements for configuring control logic and visualizing network topology in the BMS 500. For example, the user interface 505 may include, but is not limited to, one or more of windows, panels, buttons, menus, drag-and-drop areas, and / or other interactive components that allow users to create and modify control logic blocks and / or module connections within the BMS 500. The user interface 505 may display the topology view 508 and / or the programming view 506 in a unified session, such that users can switch between said views without navigating to separate tools or interfaces (e.g., the user does not have to access a separate application on the user device 504 to generate, display, access, etc. the programming view 506 and / or the topology view 508, etc. ) . For example, the user interface 505 may display a tab control, a button, and / or a menu option that allows users to toggle between the topology view 508 and / or the programming view 506 within the same session on the user device 504. The user device 504 maintains the state of the topology view 508 and the programming view 506 when switching between said views, such that changes made in the programming view 506 are reflected in the topology view 508 and vice versa without requiring users to refresh or reload the session. For example, the user device 504 may automatically update the topology view 508 when control modules and / or module connections are generated and / or modified in the programming view 506, such that the topology view 508 reflects the current configuration of the BMS 500 (e.g., without requiring manual updates to the topology view 508, etc. ) .
[0124] Referring to FIGS 6-8A, the topology view 508 may be a visual representation of the network topology (e.g., displayed via the user interface 505, etc. ) of the BMS 500 that includes (e.g., displays, etc. ) one or more control module blocks 512 (e.g., controller module block, etc. ) and one or more module connections 520 (e.g., control module connections, etc. ) therebetween. For example, the topology view 508 may display the control module blocks 512 and the module connections 520 in a hierarchical or graphical format (e.g., the user device 504 may apply a hierarchical layout algorithm to generate the topology view 508 that positions module blocks in rows and / or columns based on a depth-first and / or breadth-first traversal of the module connections 520, such that upstream module blocks are positioned above, left of, etc., downstream modules, and / or where module blocks may be positioned in parallel if in parallel workflows, etc. ) . The control module blocks 512 correspond to the control modules 511 of the controller 510, such that the topology view 508 provides for a visual representation of the control modules 511 distributed within the BMS 500 (e.g., and / or edge devices connected to the control modules 511 of the controller 510, etc. ) . For example, the control module blocks 512 are communicably coupled to the control modules 511 corresponding to the control module blocks 512 (e.g., such that updates to the control modules 511 are reflected in the control module blocks 512, and / or vice versa, etc. ) . The module connections 520 connect the control module blocks 512 to represent one or more connections (e.g., electrical connections, physical connections, communication connections, etc. ) between the control modules 511 of the controller 510 within the BMS 500.
[0125] The topology view 508 generates the control module blocks 512 and / or the module connections 520 therebetween, based on one or more control module nodes 518 and / or one or more node connections 519. For example, the control module nodes 518 may be representative of the control modules 511 of the controller 510 to define the structure of the controller 510 and / or the control modules 511 thereof within the BMS 500. The one or more control module nodes 518 may be displayed in a list view and / or a hierarchical tree within the user interface 505 (see FIGS 6 and 9) , where the topology view 508 displays the control module blocks 512 corresponding to the one or more control module nodes 518 to visually represent the control modules 511 of the controller 510.
[0126] The controller 510 may be communicable coupled to the user device 504 and may execute control logic to coordinate operations of the one or more edge devices 502 coupled to the controller 510 (e.g., via the control modules 511, etc. ) . The control modules 511 may be physically distributed across different locations within a building or campus and / or logically distributed across different processing units or computational resources within the BMS 500. In some implementations, the control modules 511 may communicate (e.g., with other control modules, with the edge devices 502 connected thereto, etc. ) via one or more communication protocols to transmit control commands, receive status updates, and / or synchronize control operations across the control module blocks 512.
[0127] The controller 510 may receive (e.g., from the edge devices 502, etc. ) and / or generate operational data (e.g., status, current setpoints, input parameters and / or values thereof, output parameters and / or values thereof, etc. ) that reflects the operational performance (e.g., state, configuration, etc. ) of the edge devices 502 connected to the control modules 511. The controller 510 may transmit the operational data for the edge devices 502 to the user device 504 to enable real-time monitoring and / or configuration adjustments (e.g., updates to the control logic, system maintenance and / or configuration, etc. ) . The user device 504 updates (e.g., automatically, etc. ) the topology view 508 (e.g., and / or the programming view 506, etc. ) based on the received operational data for the edge devices 502, such that the user interface 505 displays current the operational data (e.g., current connection states, input / output port utilization, and / or operational parameters for the edge devices 502, etc. ) via the control module blocks 512 corresponding to the control modules 511 the edge devices 502 are connected to, without requiring manual user intervention to refresh the views.
[0128] For example, the topology view 508 represents (e.g., displays, etc. ) the control modules 511 as the one or more control module blocks 512 with the module connections 520 therebetween. The module connections 520 may represent communication pathways and / or connections between the control modules 511 to exchange data, synchronize control operations, and / or coordinate operational workflows for the controller 510 for the edge devices 502 within the BMS 500. The control module blocks 512 may be automatically generated and / or updated (e.g., adjusted, modifier, changed, etc. ) by the user device 504 based on the control modules 511 being activated and / or detected within the BMS 500.
[0129] The controller 510 and / or user device 504 may generate the topology view 508 displaying the control module blocks 512 based on a network tree listing of the control modules 511 established within the BMS 500, such as in the network tree panel 517. For example, the network tree panel 517 may include the control module nodes 518 and the node connections 519 therebetween. The network tree panel 517 may be displayed on the user interface 505 on a designated portion thereof, such as a side panel relative to a graphical canvas 507 when in the programming view 506, and / or in a side panel adjacent to the control module blocks 512 when in the topology view 508. The control module blocks 512 and the module connections 520 may correspond to the control module nodes 518 and / or the node connections 519. When in the programming view 506, the control module nodes 518 and / or the node connections 519 therebetween may be generated. For example, when in the programming view 506, the control module nodes 518 may be selected and / or generated (e.g., from a selection area defined on the user interface, such as a side portion of the user interface within the programming view 506, etc. ) , such that the network tree shown in the network tree panel 517 is generated and / or adjusted. The node connections 519 may be generated via selection and / or determination of communicable connections between the control modules 511 of the controller 510 (e.g., communication with the control modules 511 to determine communication pathways therewith, etc. ) . The topology view 508 may be generated (e.g., automatically generated, etc. ) based on the control module nodes 518 and / or the node connections 519 established in the programming view 506 to provide a visual representation of the control modules 511 within the BMS 500. In some embodiments, the user device 504 may determine the control modules 511 activated in the controller 510 and / or determine the module identifiers (e.g., network addresses, communication parameters, etc. ) for the control modules 511, such that the user device 504 generates the topology view 508 to visually represent the hierarchical arrangement of the control modules 511 via the control module blocks 512 and the module connections 520 between them without requiring manual user input to specify the module topology for the controller 510 (e.g., without having to manually add a control module and / or a connection between modules, etc. ) .
[0130] For example, and as shown in FIG. 6, the control module blocks 512 may include a first control module block 513 connected (e.g., communicably coupled to, etc. ) a first control module of the controller 510 for communication with at least some of (e.g., a first subset of, etc. ) the edge devices 502. For example, the first control module block 513 represents the first control module of the controller 510 executing control logic to coordinate operations of the edge devices 502 connected thereto. In some embodiments, the control module blocks 512 may include a second control module block 514 connected (e.g., communicably coupled to, etc. ) a second control module of the controller 510 for communication with at least some of (e.g., a second subset of, etc. ) the edge devices 502. For example, the second control module block 514 represents the second control module of the controller 510 executing control logic to coordinate operations of the edge devices 502 connected thereto. The second control module block 514 may be a downstream control module of the controller 510 relative to the first control module block 513. In some embodiments, the control module blocks 512 may include a third control module block 515 connected (e.g., communicably coupled to, etc. ) a third control module of the controller 510 for communication with at least some of (e.g., a third subset of, etc. ) the edge devices 502. For example, the third control module block 514 represents the third control module of the controller 510 executing control logic to coordinate operations of the edge devices 502 connected thereto. The third control module block 515 may be a downstream control module of the controller 510 relative to the first control module block 513. For example, the second control module block 514 and the third control module block 515 may be in parallel within the topology view 508 (e.g., in the same row and / or column, such as being adjacent, etc. ) . In some embodiments, the third control module block 515 may be a downstream control module of the controller 510 relative to the second control module block 514.
[0131] The module connections 520 include one or more connection indicators indicating various type of connections between the control modules 511 (e.g., communication pathways therebetween that establish data exchange channels for transmitting operational data, and / or control signals between the control modules 511, etc. ) that are represented in the topology view 508 by the module connections 520. For example, the topology view 508 may display the connection indicators of the module connections 520 as different colors (e.g., blue, green, red, etc. ) , line styles (e.g., solid, dashed, dash-dot, etc. ) , line widths and / or different captions (e.g., connection type abbreviations, etc. ) to indicate the different communication protocols and / or connection types between the control modules 511. In some embodiments, the control modules 511 of the controller 510 may be connected via one or more of wired communication links such as Ethernet connections (e.g., which may be configured to communicate using TCP / IP communications, etc. ) , serial communication connections, or fieldbus connections, and / or wireless communication links such as Wi-Fi, Bluetooth, Zigbee, or other radio-frequency communication protocols. For example, the topology view 508 may display a first type of connection (e.g., a serial connection, etc. ) as a blue line. For another example, the topology view 508 may display a second type of connection (e.g., an Ethernet connection, etc. ) as a green line. Based on the different connection indicators displayed for the module connections 520, users can identify the communication types between the control modules 511 of the controller 510 within the BMS 500 by analyzing (e.g., viewing, etc. ) the module connections 520 between the control module blocks 512 within the topology view 508.
[0132] For example, as shown in FIG. 6, the module connections 520 may include a first module connection 521 generated and / or displayed in the topology view 508 connecting the first control module block 513 and the second control module block 514. The first module connection 521 may include a first connection indicator indicating the first type of connection (e.g., a serial connection, which may be displayed as a blue line, etc. ) between the first control module and the second control module represented by the blocks in the topology view 508. For another example, a second module connection 522 generated and / or displayed in the topology view 508 connecting the first control module block 513 and the third control module block 515. The second module connection 522 may include a second connection indicator indicating the second type of connection (e.g., an Ethernet connection, which may be displayed as a green line, etc. ) between the first control module and the third control module represented by the blocks in the topology view 508.
[0133] In some embodiments, the user device 504 may receive user input indicative of the module identifiers (e.g., a network address for the user device 504 to query and / or otherwise search, etc. ) , such that the user device 504 may detect the control modules 511 activated (e.g., deployed, connected, etc. ) within the BMS 500. For example, a user may provide user input (e.g., a network address for the user device 504 to query and / or otherwise search, etc. ) via the user interface 505 when in the programming view 506 to connect the user device 504 to the control modules 511 to determine (e.g., detect, etc. ) a number of and / or types of control modules connected to the edge devices 502. The user device 504 generates (e.g., automatically, etc. ) the control module blocks 512 based on detecting the activated control modules of the control modules 511. The user device 504 may automatically generate the control module blocks 512 corresponding to the control modules 511 within the topology view 508 based on the module identifiers (e.g., a type of control module, etc. ) for the control modules 511. Based on the module identifiers (e.g., the communication type, etc. ) , the user device 504 may generate (e.g., automatically, etc. ) the module connection 520 in the topology view 508 to reflect the communication pathways between the control modules 511. Thereby, the topology view 508 automatically generates and / or adjusts to reflect the current configuration of the BMS 500 without requiring manual user input to update the topology view 508 (e.g., once the user connects the user device 504 to the control modules 511 within the programming view 506, such as to implement the control modules 511 into the operational workflow for the edge devices 502 connected thereto and / or adjust control logic for said control modules, the topology view 508 is automatically updated accordingly, etc. ) .
[0134] In some embodiments, the control modules 511 of the controller 510 include one or more connection ports 526 to communicably couple the edge devices 502 the control modules 511. For example, the connection ports 526 may be physical connectors (e.g., ports, etc. ) on the control modules 511 and / or logical connection points of the control modules 511 (e.g., access and / or interface points for communication pathways with the control modules 511 for the edge devices 502 connected thereto, etc. ) . In some embodiments, the connection ports 526 may include, but are not limited to input / output (IO) ports, such as analog input (AI) ports or analog output (AO) ports, digital input (DI) ports or digital output (DO) ports, binary input (BI) ports or binary output (BO) ports, and / or communication ports (e.g., serial communications, Ethernet, etc. ) .
[0135] The topology view 508 may display a number of connection points 524 in the control module blocks 512 corresponding to the connection ports 526 on the control modules 511 being represented by the control module blocks 512. In some embodiments, the one or more control module nodes 518 may include the connection points 524 (e.g., within the network tree panel 517, etc. ) . The connection points 524 may be represented in the topology view 508 as visual indicators (e.g., displayed as numerical indicators, graphical badges or ports, etc., within the control module blocks 512, etc. ) , such that users can visualize the number of available connection ports and / or connected edge devices to the control modules 511 of the controller 510 within the BMS 500. In some embodiments, in the topology view 508, the control module blocks 512 may include (e.g., display, etc. ) a number of available connection points 524 (e.g., a maximum number of connection points, etc. ) for the control modules 511. The control module blocks 512 may include a number of connected (e.g., active, etc. ) connection points 524 for the control modules 511. Thereby, users can visually assess the utilization of available connection ports on the control modules 511 within the topology view 508 without querying configuration data and / or navigating to separate diagnostic interfaces.
[0136] In some embodiments, the connection portions 524 may indicate status data for the edge devices 502 connected to the control modules 511 (e.g., active, inactive, fault detected, etc. ) such that the topology view 508 reflects the current connection status of the edge devices 502 via the corresponding connection point 524 representing said edge device connection that is displayed on the topology view 508 within the control module blocks 512 (e.g., by changing a color of said connection point 524 based on the status data, etc., such that a user may visually analyze connection statuses for the edge devices 502 within the BMS 500, such as to detect a fault and / or upgrade or renew a license to fix a disconnected edge device in response to the connection point 524 representing the disconnection in the topology view 508) . Thereby, users can visually assess the connections of the edge devices 502 to the control modules 511 via the topology view 508 to detect and / or troubleshoot faulty connections with the edge devices 502 without querying configuration data and / or navigating to separate diagnostic interfaces. For example, in some embodiments, when in the topology view 508, the user device 504 may receive user input to select an individual module block of the control module blocks 512 displayed within the topology view 508 to focus on said individual block. In the focused view (e.g., a detailed view, etc. ) , such as shown in FIG. 8B, the user device 504 may display the individual module block (e.g., the first control module block 513, etc. ) for the user to visually analyze operational data for a control module represented by the individual module block. For example, the focused view from the topology view 508 may display the connection points 524 representing the status information of the edge devices 502 connected to the individual module block, such that the user may detect and / or troubleshoot faulty connections with the edge devices 502 without querying configuration data and / or navigating to separate diagnostic interfaces (see FIG. 8B) .
[0137] The user device 504 may receive user input to transition between the topology view 508 and the programming view 506, such that the user may visually analyze the control modules 511 of the controller 510 and the edge devices 502 connected thereto in the topology view 508 and / or configure control logic for the control modules 511 within the programming view 506. Referring to FIGS. 9-14, the programming view 506 may be a visual interface that represents control logic in a block-based format for configuring and / or editing operational workflows within the BMS 500 (e.g., for controlling operation of the edge devices 502 via the control modules 511 of the controller 510, etc. ) . For example, the programming view 506 may provide (e.g., generate, etc. ) one or more control logic blocks 530 defining (e.g., including, representing, etc. ) control logic that executes control operations for the edge devices 502 within the BMS 500. In some embodiments, the control logic blocks 530 may represent sensors, actuators, logic operators, mathematical functions, and / or other control elements to be interconnected to define and / or implement operational workflows for the BMS 500. For example, the control logic defined by the control logic blocks 530 (e.g., and / or the control logic connections 536 therebetween, etc. ) may be executed by the controller 510 (e.g., by the control modules 511 connected to the edge devices 502 corresponding to the control logic defined by the control logic blocks 530, etc. ) .
[0138] Within the programming view 506, the user device 504 may receive user input to generate and / or adjust the control modules 511 of the controller 510, such that the control logic blocks 530 may be generated and / or adjusted for the control modules 511 to define the operational workflow thereof. For example, in the programming view 506, available control modules may be displayed for user selection (e.g., drag-and-drop command to select, click to select, etc. ) . Once generated, the control modules 511 are generated, the user device 504 may display a hierarchical listing of the control module blocks 512 corresponding to the control modules 511 of the controller 510 in a tree view within the programming view 506 displayed in the user interface 505 (e.g., within a designated area thereof, such as a side panel such as a left-side panel, etc. ) . The hierarchical listing may include the control logic blocks 530 generated within the programming view 506 to define at least part of the operational workflow for the control modules 511 within the hierarchical listing (e.g., tree view, etc. ) . For example, the user device 504 may determine communication pathways between the control modules 511 to execute the control logic of the control logic blocks 530, such that the user device 504 generates and / or adjusts the module connections 520 between the control module blocks 512. The communication pathways may determine the hierarchical relationship between the control modules 511.
[0139] In some embodiments, the control logic blocks 530 may be represented within the programming view 506 as geometric blocks (e.g., shapes, tiles, etc. ) positioned on and / or within a graphical canvas 507 (e.g., where the graphical canvas 507 may be displayed on a middle portion of the user interface 505, etc. ) . In some embodiments, within the programming view 506, the user device 504 may receive user input to select the control modules 511 and / or the edge devices 502 connected thereto to be displayed as the control logic blocks 530 within the programming view 506 (e.g., within the graphical canvas 507 displayed on the user interface 505, etc. ) . For example, the control logic blocks 530 (e.g., available control logic blocks, etc. ) corresponding to the control modules 511 and / or the edge devices 502 may be selected from a library and / or palette displayed on the user interface 505 (e.g., in a defined portion thereof, such as a side portion, a left side, a bottom-left side portion, etc. ) . The user device 504 may receive user input to display the control logic block 530 that is selected on the user interface 505 in the graphical block format (e.g., where the control logic blocks 530 may be displayed in a list and / or as text when being selected, etc. ) . For example, the user device 504 may generate the control logic blocks 530 within the user interface 505, such as within the graphical canvas 507 (e.g., in the middle section of the user interface 505, etc. ) , in response to a selection command (e.g., the user input, etc. ) such as a drag-and-drop command, a generate command, and / or another type of command to generate the control logic blocks 530 being selected.
[0140] In the programming view 506, one or more control logic connections 536 may be formed (e.g., generated, defined, displayed, etc. ) between the control logic blocks 530 to establish at least part of the operational workflow for the BMS 500. The control logic blocks 530 and / or the control logic connections 536 therebetween may define control algorithms and / or parameter relationships between the control logic blocks 530.
[0141] The control logic blocks 530 may include one or more input / output (IO) parameters 534 defining variable types and / or values thereof included within the control logic to at least partially define the operational workflow for the BMS 500 (e.g., the IO parameters 534 may be variables that control logic steps use to make operational decisions, and / or values for variables that are input into a mathematical operation within the operational workflow, etc. ) . For example, the IO parameters 534 may be data elements within the control logic blocks 530 that specify input values to be implemented by the control logic operations defined within the control logic blocks 530, output values to be determined and / or provided by the control logic operations defined within the control logic blocks 530, and / or data connection points through which data may flow between the control logic blocks 530 in the operational workflow. For example, the IO parameters 534 may be scalar data fields that store numerical values, boolean values, enumeration values, and / or string values that define operational variables (e.g., parameters, etc. ) within the control logic block 530. The IO parameters 534 may provide data connection points, such that an output parameter may provide data to a downstream control logic block that is received by an input parameter of said downstream control logic block. In some embodiments, the IO parameters 534 may include, but are not limited to, device address parameters that specify a network address for the control modules 511 and / or the edge devices 502, device identifiers, connection (e.g., communication, etc. ) port numbers for the edge devices 502 connected to the control modules 511 associated with the control logic blocks 530, communication protocol types and / or identifiers, signal value parameters that specify measurement values, command values, and / or status indicator values to be transmitted or received, threshold value parameters that specify comparison thresholds, alarm limits, and / or range boundaries used in conditional logic operations, and / or timing parameters that specify sampling intervals, control update periods, and / or delay values that govern temporal aspects of control logic execution.
[0142] For example, the control logic connections 536 may be formed (e.g., defined, displayed, etc. ) between the IO parameters 534 of the control logic blocks 530 (e.g., defined from an output parameter of one control logic block to a corresponding input parameter of another control logic block, etc. ) . In some embodiments, the control logic connections 536 may be formed between the IO parameters 534 corresponding to each other on different control logic blocks of the control logic blocks 530 (e.g., an output parameter of one control logic block may only be connected to a corresponding input parameter of another control logic block, the input parameter being the same type of parameter as the output parameter, etc. ) . In some embodiments, the user device 504 may receive user input to establish the control logic connections 536 between the control logic blocks 530, such as the IO parameters 534 thereof (e.g., via dragging commands between the control logic blocks 530, via click commands to select the control logic blocks 530 to be connected, etc. ) .
[0143] For example, such as shown in FIGS. 13 and 14, when in the programming view 506, a first control logic connection 537 may be formed between a first control logic block 531 and a second control logic block 532. The second control logic block 532 may be downstream of the first control logic block 531. For example, the first control logic connection 537 may be formed between an output parameter (e.g., of the IO parameters 534, etc. ) of the first control logic block 531 and an input parameter (e.g., of the IO parameters 534, etc. ) of the second control logic block 532. The first control logic connection 537 may be a visual representation of a data flow pathway between the first control logic block 531 and the second control logic block 532 to define an operational relationship of the operational workflow for the BMS 500.
[0144] A second control logic connection 538 may be formed between the first control logic block 531 and a third control logic block 533. The first control logic block 531 may be downstream of the third control logic block 533. For example, the second control logic connection 538 may be formed between an output parameter (e.g., of the IO parameters 534, etc. ) of the third control logic block 533 and an input parameter (e.g., of the IO parameters 534, etc. ) of the first control logic block 531. The second control logic connection 538 may be a visual representation of a data flow pathway between the first control logic block 531 and the third control logic block 533 to define an operational relationship of the operational workflow for the BMS 500.
[0145] In some embodiments, the first control logic connection 537 and the second control logic connection 538 define operational relationships between the first control logic block 531, the second control logic block 532, and the third control logic block 533 to at least partially define the operational workflow for the BMS 500 (e.g., defining an operational flow for implementing the output parameter of the third control logic block 533 through the control logic defined by the control logic blocks 530, etc. ) . In some embodiments, the second control logic connection 538 may be automatically adjusted (e.g., generated, modified, changes, edited, etc. ) by the user device 504 based on adjusting the first control logic connection 537. Thereby, the user device 504 can maintain operational consistency across the control logic blocks 530 when the operational workflow is adjusted within the programming view 506, such as by adjusting the first control logic connection 537 and adjusting the second control logic connection 538 accordingly (e.g., carrying adjustments through the operational workflow between the control logic blocks 530, etc. ) .
[0146] Referring to FIGS 9-14, the IO parameters 534 may be adjusted (e.g., directly, etc. ) in the programming view 506 to modify the control logic blocks 530 (e.g., the control logic thereof, etc. ) that defines the operational workflow for the edge devices 502. In some embodiments, the user device 504 may receive user input, when in the programming view 506, to adjust a value of the IO parameters 534 by entering text into a text entry field (see FIGS 12A-12B) , selecting an option from a drop-down menu (see FIGS 11A-11B) , and / or generating (e.g., adjusting, such as by dragging, etc. ) a control logic connection between the control logic blocks 530 (e.g., the IO parameters 534 thereof, etc. ) (see FIG. 13) . In some embodiments, the user input when in the programming view 506 to adjust a value of the IO parameters 534 may include a hover-and-click operation for the user to select a IO parameter of the IO parameters 534, select and / or enter a value for said IO parameter, and / or confirm (e.g., via a click, etc. ) the adjustment to the value of said IO parameter (e.g., see FIG. 11B for hovering and selecting a value from a drop-down menu after selecting the IO parameter of the IO parameters 534, and / or see FIG. 12B for hovering and entering a value for said IO parameter via a text entry field, etc. ) . Modifying the IO parameter values adjusts control algorithm coefficients, threshold values, setpoint values, and / or data routing pathways executed by the control logic block 530 during operation of the BMS 500.
[0147] The control logic blocks 530 are expandable within (e.g., directly, etc. ) the programming view 506 (e.g., within the graphical canvas 507 displaying the control logic blocks 530 in a graphical block format, etc. ) . Expanding the control logic blocks 530 may display a configuration panel and / or expand the configuration panel to reveal editable (e.g., adjustable, modifiable, etc. ) IO parameter fields, data types, value constraints, and / or connection points associated with the control logic blocks 530. For example, the control logic blocks 530 may be selected to display configuration fields and / or additional configuration fields, such as the IO parameters 534, within the programming view 506 (e.g., within the graphical canvas 507 thereof, etc. ) . The user device 504 may receive user input to select and / or expand the control logic blocks 530 to display the IO parameters 534 for forming the control logic connections 536 between the IO parameters 534 of the control logic blocks 530.
[0148] In some embodiments, the programming view 506 may display a configuration panel in a designated area of the user interface 505 (e.g., a side region such as a right-side portion, etc. ) when the control logic blocks 530 are selected within the user interface 505 (e.g., in block format within the graphical canvas 507 thereof, etc. ) . The configuration panel may display the IO parameters 534 as a list of said parameters that are adjustable within the configuration panel (e.g., where data values of the IO parameters 534 may be adjusted via text entry fields, drop-down menus, and / or numerical sliders, etc. ) . Adjustments made in the configuration panel to the IO parameters 534 are automatically mirrored in the control logic blocks 530 displayed on the user interface 505 (e.g., within the graphical canvas 507 thereof, etc. ) . Thereby, the programming view 506 provides for adjustments to control logic defining the operational workflow within the BMS 500, such that a user can visualize the operational workflow within the programming view 506 while making adjusts to the control logic, which improves the efficiency and / or accuracy of control logic adjustments within the BMS 500.
[0149] The user device 504 may update the topology view 508 based on adjustment made in the programming view 506, such that the topology view 508 reflects the current configuration of the BMS 500 without requiring manual user input to refresh or regenerate the topology view 508. For example, the user device 504 may determine that the control logic blocks 530 are generated and / or adjusted within the programming view 506 (e.g., within the graphical canvas 507 thereof, etc. ) , such that the user device 504 generates and / or adjusts the topology view 508 to generate the control module blocks 512 corresponding to control modules 511 configured to execute the control logic defined by the control logic blocks 530. The control modules 511 generated and / or adjusted within the programming view 506, such as defining operational workflow for the control modules 511, may be displayed via the corresponding control module blocks 512 in the hierarchical listing (e.g., tree view, etc. ) , such that the user device 504 may automatically generate the topology view 508 based on the hierarchical listing so the user can visualize the distribution and / or connections of the control modules 511 of the controller 510 within the BMS 500. Thereby, the BMS 500 can provide the user interface 505 displaying a block-based programming view 506 that allows users to edit control logic directly and visualize the operational workflow for the BMS 500, and the user interface 505 can display the topology view 508 to track distribution of the control modules 511 and / or connections with the edge devices 502 thereto, such that users can understand the relationships between the control logic blocks 530 and the edge devices 502 as implemented by the control modules 511 of the controller 510, which improves the efficiency of configuring building management systems by reducing the need to manually synchronize programming and topology views and / or switch between interfaces to program and / or visually analyze the networked system.
[0150] Referring to FIG. 15, a method 600 of implementing a building management system (BMS) is depicted. The method 600 may be executed, performed, and / or otherwise carried out by any embodiment of the BMS 500, as described herein. In some embodiments, the method 600 may include additional, fewer, and / or a different order of method steps (e.g., operations, etc. ) .
[0151] The method 600 may include connecting one or more edge devices within the building management system via one or more control modules of a controller, at step 610. For example, the one or more control modules are communicably coupled to the one or more edge devices to execute control logic defining the operational workflow for the one or more edge devices. The one or more control modules may be distributed across the BMS, where subsets of edge devices are coupled to the modules to control operation thereof. For example, the BMS may include, but is not limited to including, temperature sensors, humidity sensors, damper actuators, fan actuators, valve actuators, HVAC equipment, lighting systems, and / or water management equipment, which is communicably coupled to the various control modules of the controller (e.g., to exchange data and / or control signals therebetween to implement the operational workflow for the edge devices, etc. ) . In some embodiments, the control modules of the controller may be the control modules 511 of the controller 510, as described herein.
[0152] In some embodiments, the control modules of the controller may be communicably coupled to each other via one or more of Ethernet connections, serial communication connections, fieldbus connections, and / or wireless communication pathways. In some embodiments, the control module connections may be formed in response to user input that specifies device identifiers, network addresses, and / or communication protocol types, such that configuration data is transmitted to the controller based on the user input and the controller establishes communication sessions between the control modules. In some embodiments, the connections between the control modules may occur automatically based on network discovery protocols without requiring explicit user input to specify connection parameters. The control modules may receive configuration data and establish communication sessions with the other control modules using the specified parameters. In some embodiments, the control modules may be physically connected (e.g., electrically wired connections, mechanical connections to physically attach control modules together, etc. ) .
[0153] The method 600 may include generating a user interface displaying a programming view including a plurality of control logic blocks including control logic at least partially defining the operational workflow for the edge devices, at step 620. The user interface displaying the programming view may be generated by a user device. For example, the programming view may be the programming view 506 displayed on the user interface 505 provided by the user device 504, as described herein. The user device is communicably coupled to the controller. In some embodiments, the user device may be the controller, such that the user interface is generated by the controller. The programming view may be a visual interface that displays control logic in a block-based format for configuring operational workflows within the BMS. For example, the programming view may include and / or display a graphical canvas where control logic blocks (e.g., representing edge devices, such as sensors, actuators, valves, etc., logic operators, and / or mathematical function blocks, etc. ) may be generated, arranged, connected, and / or configured to define the operational workflow for the edge devices to be executed by the control modules of the controller. One or more control logic connections may be formed (e.g., generated, defined, etc. ) between the control logic blocks. For example, the control logic connections may be defined between input / output parameters of the control logic blocks. The control logic connections at least partially define the operational workflow for the edge devices, as the control logic connections define operational relationships between the input / output parameters of the control logic blocks (e.g., define a downstream direction of the operational workflow, and / or control loops and / or threshold values for moving between the control logic blocks, etc. ) . For example, the control logic blocks may be the control logic blocks 530, as described herein, which may be connected by the module connections 520, as described herein.
[0154] In some embodiments, the user device may display a hierarchical listing of the control modules within the programming view, such that the programing view may provide for generating and / or adjusting control logic defining the operational workflow to be executed by the control module. Available control modules may be displayed in a designated area (e.g., selection area, etc. ) defined in a portion of the user interface when in the programming view (e.g., in a left side panel and / or pallet, etc. ) . The control logic may be selected for generating and / or adjusting control logic for said control module (e.g., selected by user input, such as choosing a control module from a listing of available control modules, etc. ) . In some embodiments, a user may drag the control logic blocks onto the graphical canvas (e.g., from a selection area defined on the user interface, such as a side portion of the user interface within the programming view, etc. ) , such that the user device generates a control logic block within the graphical canvas (e.g., a control logic block representing an edge device, a mathematical operation, a control logic operation, etc. ) . For example, after the selection of a control module, the user device may determine and / or provide (e.g., via a list in the selection area of the user interface, etc. ) available control logic blocks for the operational workflow to be executed by the selected control module.
[0155] The control logic blocks include one or more input / output parameters corresponding to data output and / or inputs for the control logic defined within the control logic blocks (e.g., for the blocks to use inputs for the control logic determinations and / or provide the outputs for use in downstream control logic within the operational workflow, etc. ) . The one or more control logic connections may be formed (e.g., generated, defined, etc. ) between the input / output parameters of the control logic blocks (e.g., to feed output parameter values into the corresponding input parameters of downstream blocks within the operational workflow, etc. ) . In some embodiments, the control logic blocks may be expandable within the programming view (e.g., when displayed within the graphical canvas thereof, etc. ) . For example, expanding the control logic blocks displays operational parameters and / or additional operational parameters (e.g., configuration fields and / or additional configuration fields, etc. ) , including the input / output parameters and / or additional input / output parameters. In some embodiments, the user device may receive user input to expand the control logic block to reveal configuration fields and / or additional configuration fields, such as editable parameter fields, data types, value constraints, and / or connection points associated with the control logic block directly within the user interface displaying the programming view. The control logic blocks may be adjusted, such as adjusting values for the input / output parameters thereof, and / or the control logic connections may be formed between control logic blocks directly in the programming interface (e.g., the graphical canvas, etc. ) . Thereby, the operational workflow may be adjusted within the programming view without navigating to separate configuration tool, which increases configuration and / or programming efficiency for the BMS.
[0156] The method 600 may include adjusting, via the programming view, one or more operational parameters within the one or more control logic blocks to adjust the operational workflow for the edge devices, at step 630. For example, the operational parameters may be and / or include the input / output parameters of the control logic blocks and / or the control logic connections therebetween. In some embodiments, the user device may adjust the one or more operational parameters by receiving user input directly within the programming view (e.g., the graphical canvas thereof, etc. ) that modifies (e.g., adjusts, etc. ) the operational parameters of the control logic blocks. The operational parameters may have values adjusted (e.g., directly within the graphical canvas, etc. ) via text entry fields, drop-down menus, numerical sliders, and / or other input controls displayed in the control logic blocks. In some embodiments, the operational parameters for a selected control logic block may be displayed within a designated configuration area (e.g., designated portion of the user interface within the programming view, such as a side panel thereof, etc. ) within the programming view that displays the operational parameters for the selected control logic block and / or provides for adjustment of said operational parameters. The control logic blocks being adjustable directly within the programming view provides for the user to visualize the operational workflow for the edge devices while adjusting said operational workflow, which increases the efficiency and / or accuracy of programming the operational workflow to be executed by a control module of the controller for the BMS (e.g., where the user would otherwise switch between interfaces to adjust the control logic and visualize the workflow, and / or be unable to visualize said workflow, etc. ) .
[0157] In some embodiments, the user device transmits the operational workflow to the control modules of the controller in response to adjusting operational parameters of the control logic blocks within the programming view (e.g., to update the operational workflow implemented by said control modules, etc. ) . For example, the operational workflow and / or updated operational workflow specifies the modified operational parameter values (e.g., threshold values, setpoint values, etc. ) , modified control logic relationships, and / or modified data flow pathways defined by the control logic connections in the programming view. The control modules of the controller may receive the operational workflow from the user device. For example, the control modules can execute the operational workflow for the edge devices by executing the control logic defined within the programming view (e.g., by transmitting control commands to the edge devices according to the operational parameter values and / or the data flow pathways generated and / or adjusted within the programming view, etc. ) .
[0158] The method 600 may include automatically generating a topology view of the modules of the controller, the topology view comprising one or more module blocks representative of the modules, where the one or more module blocks are connected by the one or more module connections, at step 640. For example, the method 600 may include generating the one or more module connections between the module blocks. The module blocks may be communicably coupled to the modules of the controller (e.g., to communicate operational data and control logic therebetween, etc. ) .
[0159] The topology view may be a visual representation of the network topology of the BMS that displays the control modules and / or module connections in a hierarchical and / or graphical format. For example, the user can visually determine which control modules are connected to which edge devices within the BMS via the topology view. In some embodiments, the module blocks may be displayed as geometric shapes within the topology view. For example, each module block may correspond to a respective control module of the controller, which may be connected by the module connections to visually represent communication pathways between the corresponding control modules. In some embodiments, the topology view may display the control module blocks in the hierarchical layout, such that the module blocks are displayed on the user interface in rows and / or columns based on a depth-first and / or breadth-first traversal of the module connections (e.g., where upstream modules may be positioned above and / or to the left of downstream modules in the topology view, etc. ) .
[0160] Different types of module connections may be displayed differently when in the topology view. For example, the module connections may be displayed differently based on a module connection indicator indicating a type of module connection (e.g., wired connections such as Ethernet and / or serial connections, and / or wireless connections such as Wi-Fi and / or Bluetooth, etc. ) . In some embodiments, the module connections may be displayed on the user interface when in the topology view in different colors, line styles, line widths, and / or with line captions to indicate different communication protocols and / or connection types between the control modules. Thereby, users can identify the various communication protocols and / or connection types between the control modules forming the controller by visual analysis in the topology view (e.g., where users would otherwise have to navigate between separate configuration interfaces and / or inspect connection parameters in textual form, etc. ) .
[0161] The topology view may be automatically generated in response to changes in the programming view, such that the topology view is updated without requiring manual user input when control modules are added or adjusted, module connections are generated and / or adjusted, and / or edge devices are connected and / or adjusted within the programming view. The topology view may be automatically generated in response to adjusts to the control modules, module connections, and / or edge devices within the BMS (e.g., in response to physical changes to the devices of the BMS, which are reflected via the topology view so the user can visually assess said changes, and / or adjust the operational workflow accordingly in the programming view, etc. ) . For example, the method 600 may include generating, via the programming view, one or more control module nodes corresponding to the modules of the controller. One or more node connections between the control module nodes may be generated in the programming view, where the node connections are indicative of modules of the edge controller being communicably coupled. The topology view (e.g., the control module blocks and the module connections, etc. ) may be updated (e.g., automatically generated, etc. ) based on the control module nodes and the control module connections.
[0162] In some embodiments, a number of connected input / output points for the plurality of module blocks may be displayed in the topology view, based on a number of connected input / output ports for edge devices connected to a first module of the controller within the BMS. For example, based on port utilization data from the control modules, the user device may identify the number of input / output ports on the control modules currently connected to edge devices, such that the user may display numerical indicators and / or graphical badges on the control module blocks displayed in the topology view. Thereby, users can visually assess the number of connected input / output points for each control module within the BMS, such that the user can determine a distribution of edge devices and / or an opportunity to adjust a number of control modules within the controller (e.g., to acquire more control modules to connect additional edge devices, and / or decrease control modules because of inefficient distribution of connected edge devices, etc. ) .
[0163] In some embodiments, the topology view may provide for zoom capabilities that allow users to adjust the display scale of the topology view to show global information for the BMS when zoomed out and / or detailed information for the operational workflow when zoomed in. In some embodiments, when in the topology view, an individual control module block may be selected, such that one or more connection points are visually displayed. The connection points correspond to the connection ports of the corresponding control module, where the connection points may include a connection point indicator to indicate a status of the edge device connected thereto (e.g., good / proper connection, disconnection, no license for the edge device, etc. ) .
[0164] The method 600, when implemented, provides for the display block-based representative control module blocks and / or control logic within a single session on the user device, such that users can understand the relationships between control logic blocks, edge devices, and / or the control modules executing said control logic to implement the operational workflow for said edge devices. In the programming view, the method 600 provides for editing control logic directly, while visualizing the operational workflow for the BMS. In the topology view, the method 600 provides for displaying control module distribution and edge device connections across the BMS, such that the distributions can be tracked and / or visually analyzed for BMS improvement decisions (e.g., to expand, reorganize, and / or optimize the BMS, etc. ) . Thereby, the method 600 improves the efficiency of configuring building management systems by reducing the need to manually synchronize programming and topology views, such that users can visually analyze control and / or edge devices within the BMS while configuring said devices for efficient operation of the BMS. Configuration of Exemplary Embodiments
[0165] 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 can be reversed or otherwise varied and the nature or number of discrete elements or positions can 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 can be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions can be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.
[0166] The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure can 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 comprise 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.
[0167] 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 can 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.
Claims
1.An edge controller for a building management system, the edge controller comprising:one or more modules communicably coupled to one or more edge devices to implement an operational workflow for the one or more edge devices, the one or more modules comprising processing circuitry configured to:generate, via a programming view, one or more control module nodes corresponding to the one or more modules of the edge controller, one or more node connections between the control module nodes indicative of modules of the edge controller being communicably coupled, and one or more control logic blocks to be executed by the modules of the edge controller, the control logic blocks including control logic for operation of the edge devices;adjust, via the programming view, one or more operational parameters within the one or more control logic blocks to adjust the operational workflow for the edge devices;generate a topology view of the modules of the edge controller by displaying one or more module blocks corresponding to the one or more control module nodes representative of the modules of the edge controller, wherein the one or more module blocks are connected by one or more module connections; andoperate the one or more edge devices to adjust at least one condition within a building or campus using the operational workflow.2.The edge controller of claim 1, wherein the edge controller is further configured to display the topology view and the programming view in a unified session on a user interface.3.The edge controller of claim 1, wherein a first module block comprises one or more input / output (IO) connection points that correspond to one or more IO connection ports on a first edge device communicably coupled to the first module block.4.The edge controller of claim 3, wherein edge controller is configured to display, via the topology view, a number of connected input / output connection points for the first module block.5.The edge controller of claim 1, wherein the module blocks comprise a first module block and a second module block connected thereto by a first module connection, the second module block downstream of the first module block.6.The edge controller of claim 5, wherein the edge controller is configured to display the first module connection including a first connection indicator, the first connection indicator indicating a first type of connection between the first module block and the second module block.7.The edge controller of claim 6, wherein the first type of connection is an Ethernet connection or a serial communication connection and the edge controller comprises a plurality of Ethernet ports configured to communicate using TCP / IP communications.8.The edge controller of claim 6, wherein the edge controller is configured to automatically adjust the topology view, based on forming the control module nodes and the node connections therebetween in the programming view.9.The edge controller of claim 1, wherein the edge controller is further configured to generate, via the programming view, one or more control logic connections between the one or more control logic blocks to define the operational workflow for the one or more edge devices.10.The edge controller of claim 9, wherein the control logic blocks include one or more input / output parameters, and the programming view is configured to generate or adjust the one or more control logic connections between the input / output parameters of the control logic blocks.11.The edge controller of claim 1, wherein the control logic blocks include one or more input / output parameters, the one or more control logic connections formed between the input / output parameters of the control logic blocks via user input on a user interface.12.The edge controller of claim 11, wherein a first control logic block comprises one or more input / output parameters, and wherein the first control logic block is expandable within the user interface to adjust values for the one or more input / output parameters.13.The edge controller of claim 11, wherein the edge controller is configured to automatically adjust a second control logic connection between blocks of the control logic blocks, based on forming a first control logic connection between the first control logic block and a second control logic block.14.A method for implementing a building management system (BMS) , the method comprising:connecting one or more edge devices within the BMS via one or more modules of a controller, the one or more modules communicably coupled to the one or more edge devices to implement an operational workflow for the one or more edge devices;generating a user interface displaying a programming view comprising a plurality of control logic blocks including control logic to be executed by the modules of the controller, the plurality of control logic blocks to define the operational workflow for the edge devices within the BMS;adjusting, via the programming view, one or more operational parameters within the one or more control logic blocks to adjust the operational workflow for the edge devices; andgenerating a topology view of the modules of the controller, the topology view comprising one or more module blocks communicably coupled to the modules of the controller, the module blocks representative of the modules, wherein the one or more module blocks are connected by one or more module connections.15.The method of claim 14, further comprising displaying a first module connection between a first module block and a second module block downstream of the first module block, the first module connection including a first connection indicator indicating a first type of connection between the first module block and the second module block.16.The method of claim 14, further comprising displaying, via the topology view, a number of connected input / output points for the plurality of module blocks based on a number of connected input / output ports for edge devices connected to a first module of the controller.17.The method of claim 14, wherein the programming view and the topology view are both generated in a unified session on the user interface.18.The method of claim 14, further comprising generating, via the programming view, one or more control module nodes corresponding to the modules of the controller, and one or more node connections between the control module nodes indicative of modules of the edge controller being communicably coupled.19.The method of claim 14, further comprising expanding a first control logic block of the plurality of control logic blocks, in the programming view, to display one or more input / output parameters for the first control logic block.20.A building management system comprising:one or more edge devices operably coupled to building equipment configured to adjust at least one condition within a building or campus;an edge controller comprising one or more modules communicably coupled to the one or more edge devices to implement an operational workflow for the one or more edge devices; anda user device communicably coupled to the edge devices and the edge controller, the user device providing a user interface, and the user device configured to:generate, via a programming view, one or more control module nodes corresponding to the one or more modules of the edge controller, one or more node connections between the control module nodes indicative of modules of the edge controller being communicably coupled, and one or more control logic blocks to be executed by the modules of the edge controller, the control logic blocks including control logic for operation of the edge devices;adjust, via the programming view, one or more operational parameters within the one or more control logic blocks to adjust the operational workflow for the edge devices; andgenerate a topology view of the modules of the edge controller by displaying one or more module blocks corresponding to the one or more control module nodes representative of the modules of the edge controller, wherein the one or more module blocks are connected by one or more module connections.
