Abstract: Embodiments of the present disclosure relate to a system and a method for enabling cloud-based configuration of building management system (BMS) controllers. The system comprises a cloud configuration platform (102A) hosted on a cloud-based server (101), communicatively coupled to one or more BMS controllers (103) and a plurality of subsystems (104-1 to 104-N) on-premises of a building. The platform includes modules for defining building-related information, selecting BMS controllers, identifying subsystems, and mapping input/output parameters to respective ports. The configuration process dynamically generates machine-readable configuration files based on received input and output parameters, which are stored in a database. The configuration file is then sent to the selected BMS controller for automatic configuration of corresponding I/O ports, thereby providing an efficient, remote configuration of BMS controllers, reducing the need for physical access and thorough manual intervention, while ensuring error-free configuration of the BMS controllers. Fig. 1
DESC:EARLIEST PRIORITY DATE:
This Application claims priority from a provisional patent application filed in India having Patent Application No. 202321079741, filed on December 23, 2023, and titled “A SYSTEM AND A METHOD TO CONFIGURE CONTROLLERS OF BUILDING MANAGEMENT SYSTEMS”.
FIELD OF INVENTION
[0001] Embodiments of the present disclosure relate to building management controllers. More particularly, embodiments of the present disclosure relate to system and method for cloud-based configuration of building management controller(s).
BACKGROUND
[0002] Building Management Systems (BMS) are critical for the efficient operation and management of a building's various subsystems, including, but not limited to, HVAC, lighting, security, fire safety, water management, and energy management. These systems are responsible for maintaining comfort, safety, and energy efficiency within a building by controlling and monitoring various devices. A BMS generally consists of a network of controllers that communicate with and regulate these subsystems based on user-defined settings.
[0003] The configuration of BMS controllers is a fundamental task that ensures the subsystem operates as intended. In traditional BMS, a centralized controller is typically employed to manage and coordinate the operation of most subsystems within the building. In such a centralized architecture, if the central controller fails due to hardware issues, software bugs, or other problems, the entire BMS may stop functioning or become unreliable, potentially disrupting building operations. This centralized architecture can also present limitations in terms of scalability, flexibility, and fault tolerance.
[0004] Moreover, configuring a BMS, especially in large-scale buildings, is a complex and time-consuming process. The need for manual intervention, such as technicians physically accessing the centralized controller to perform the necessary setup, becomes even more cumbersome as the subsystems grow complex. Furthermore, the variety of subsystems such as HVAC, lighting, and security systems require configuring the centralized controller with distinct parameters for each subsystem. As the subsystems grow, this configuration process becomes increasingly difficult and inefficient, creating potential for errors, delays, and higher operational costs.
[0005] For instance, a manager (or a system integrator) may need to manually configure the centralized controller based on the device type, brand, model, and input/output parameters, which is a time-consuming and labor-intensive process. This configuration process is archaic in nature, often requiring physical connections between the centralized controller and external applications or systems to enable the necessary setup. In many cases, this means that technicians must be physically present at the controller to establish these connections, which limits the flexibility and speed of the configuration process. Furthermore, if a centralized controller needs to be configured to work with different subsystems, the manager may need to repeat this process multiple times for each subsystem across different areas of the building. This manual, one-by-one configuration approach not only increases the time and effort required but also introduces the potential for human error, especially when dealing with subsystems from multiple manufacturers or differing technologies. The reliance on physical connections further compounds these challenges, making it difficult to adapt to dynamic building needs or implement system updates efficiently.
[0006] In addition, when managing multiple buildings or large facilities, the configuration process becomes even more complicated. Each building may have different equipment, subsystems, and communication protocols, requiring individualized configuration for each site. A project manager overseeing several buildings or floors would need to configure the controllers of each building individually, even if the equipment in each building is similar. This adds a significant amount of operational complexity and increases the cost of deployment and maintenance. Moreover, this configuration process is one-to-one, meaning only one controller can be physically connected to the application at any given time, further compounding the challenge. This limitation significantly increases the timelines required to complete the configuration for multiple buildings or subsystems, as the manager must manually connect and configure each controller individually, resulting in delays and inefficiencies in project execution.
[0007] As the scale of buildings and the variety of subsystems grow, the need for a more streamlined and less error-prone method of configuring BMS controllers becomes critical. Thus, there is a pressing need for a solution that can simplify the process, reduce the manual effort involved, and allow for efficient configuration of controllers across large and complex building environments.
BRIEF DESCRIPTION
[0008] In accordance with an embodiment of the present disclosure, a system is provided for enabling cloud-based configuration of building management system (BMS) controllers. The system includes a cloud configuration system hosted on a cloud-based server, comprising a cloud configuration platform. The system further includes a plurality of subsystems on-premises of a building, and one or more BMS controllers that are communicatively coupled to the cloud configuration system. Each BMS controller of the one or more BMS controllers is communicatively and operably coupled to a respective subsystem. The cloud configuration platform comprises several modules, including a space identification module for defining building-related information, a controller selection module for selecting a BMS controller, and a subsystem identification module for selecting a subsystem to be monitored or controlled. The system further includes an input configuration module and an output configuration module for mapping respective parameters to the BMS controller's ports. The system dynamically generates a machine-readable configuration file, validates the same through a processing, identifies errors, and generates an alert to the manager for correction. The manager can re-enter and re-map corrected input and/or output parameters, after which the updated configuration file is sent to the BMS controller. The BMS controller then automatically configures the corresponding I/O ports based on the received configuration file.
[0009] In accordance with another embodiment of the present disclosure, a method for enabling cloud-based configuration of one or more building management system (BMS) controllers is provided. The method includes hosting a cloud configuration system on a cloud-based server, comprising a cloud configuration platform. The method further includes communicatively coupling one or more BMS controllers to the cloud configuration system. The method further includes defining building-related information, such as building names, number of floors, units, and zones, by a space identification module of the cloud configuration platform. Further, the method includes selecting a BMS controller from the one or more BMS controllers using a controller selection module. The method further includes selecting a subsystem from the plurality of subsystems to be controlled or monitored by the selected BMS controller using a subsystem identification module. Further, the method includes retrieving a registry file specific to the selected subsystem from a database of the cloud configuration system. The method further includes receiving input parameters for input ports and output parameters for output ports of the selected BMS controller and mapping the respective parameters to the respective ports using input and output configuration modules. The method includes dynamically generating a machine-readable configuration file based on the received input and output parameters and storing the configuration file in the database. The method further includes running a processing of the generated configuration file using a processing module to validate its compatibility and functionality with the subsystem. The method includes identifying errors in the input or output parameters based on the retrieved registry file and generating an alert to notify the manager. The method further includes enabling the manager to re-enter the corrected parameters, re-mapping the corrected input parameters and/or corrected output parameters to corresponding I/O ports of the BMS controller and dynamically updating the configuration file based on the corrected parameters. Even further, the method includes sending the updated configuration file to the selected BMS controller, wherein the controller automatically configures its I/O ports based on the received configuration file
[0010] To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will follow by reference to specific embodiments thereof, which are illustrated in the appended figures. It is to be appreciated that these figures depict only typical embodiments of the disclosure and are therefore not to be considered limiting in scope. The disclosure will be described and explained with additional specificity and detail with the appended figures.
BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The disclosure will be described and explained with additional specificity and detail with the accompanying figures in which:
[0012] FIG. 1 illustrates a block diagram representation of network architecture or an exemplary system having a cloud configuration system in communication with one or more BMS controllers in accordance with an embodiment of the present disclosure;
[0013] FIG. 2 illustrates a block diagram representation of cloud configuration platform in accordance with another embodiment of the present disclosure;
[0014] FIGS. 3-6 depict a flow chart representing the steps involved in a method for enabling cloud-based configuration of one or more building management system (BMS) controllers in accordance with yet another embodiment of the present disclosure;
[0015] Further, those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.
DETAILED DESCRIPTION
[0016] For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiment illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.
[0017] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or subsystems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but not necessarily do, all refer to the same embodiment.
[0018] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.
[0019] In the following specification and the claims, reference will be made to a number of terms, which shall be defined to have the following meanings. The singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise.
[0020] In accordance with an embodiment of the present disclosure, a system is provided for enabling cloud-based configuration of building management system (BMS) controllers. The system includes a cloud configuration system hosted on a cloud-based server, comprising a cloud configuration platform. The system further includes a plurality of subsystems on-premises of a building, and one or more BMS controllers that are communicatively coupled to the cloud configuration system. Each BMS controller of the one or more BMS controllers is communicatively and operably coupled to a respective subsystem. The cloud configuration platform comprises several modules, including a space identification module for defining building-related information, a controller selection module for selecting a BMS controller, and a subsystem identification module for selecting a subsystem to be monitored or controlled. The system further includes an input configuration module and an output configuration module for mapping respective parameters to the BMS controller's ports. The system dynamically generates a machine-readable configuration file, validates the same through a processing, identifies errors, and generates an alert to the manager for correction. The manager can re-enter and re-map corrected input and/or output parameters, after which the updated configuration file is sent to the BMS controller. The BMS controller then automatically configures the corresponding I/O ports based on the received configuration file.
[0021] FIG. 1 illustrates a block diagram representation of network architecture or an exemplary system 100 having a cloud configuration system in communication with one or more BMS controllers in accordance with an embodiment of the present disclosure. As illustrated therein, the system 100 may include a cloud configuration system 102 hosted on a cloud-based server 101. The cloud-based server 101 may represent a single computer server or a collection of computer servers. Further, the cloud-based server 101 may include one or more processors (not shown).
[0022] The cloud configuration system 102 may include a cloud configuration platform 102A. The system may include one or more BMS controllers 103 provided in-premises of a building. For illustrative purposes, a single BMS controller is shown in the figure. However, it is to be understood that, in practice, a greater number of BMS controllers may be deployed and configured as required for the efficient control or monitoring of various subsystems within the building, in a manner similar to that described in the present disclosure. Further, it may be noted that the term "building" as referred to herein may also encompass a portion of an actual building. Moreover, in an actual implementation, a single BMS controller may control or monitor multiple subsystems, or each BMS controller may control or monitor a corresponding subsystem. The present disclosure is not limited to these examples.
[0023] The one or more BMS controllers 103 may be communicatively coupled to the cloud configuration system 102 using a wired or wireless network. For example, the wired network may be an ethernet connection, and the wireless network may be Wi-Fi or Bluetooth. For example, in a wired type of connection, the one or more BMS controllers 103 connect to the cloud configuration system 102 through physical cables, such as Ethernet, providing a stable and high-speed data transfer pathway as wired connections are less susceptible to interference from external factors (e.g., environmental obstacles, electronic interference) that can affect signal strength, making them highly reliable for critical building operations. This type of connection may be preferable in an environment where wireless network stability is poor or where a consistent, high-speed connection is essential, a wired connection is preferred. For instance, in buildings with heavy electronic interference, thick walls, or multiple floors, wireless signals may weaken or drop. Here, a wired connection ensures that the one or more BMS controllers 103 can communicate seamlessly with the cloud configuration system 102, avoiding interruptions that could impact control over key systems like HVAC, lighting, and security.
[0024] On the other hand, the wireless network type of connection provides flexibility by allowing the one or more BMS controllers 103 to connect to the cloud configuration system 102 without physical cables. This setup is especially beneficial in buildings where laying cables is impractical or where flexibility in device placement is needed. In another example, if the building experiences inconsistent wireless network performance, a hybrid approach may be employed. The one or more BMS controllers 103 may use a wired connection for primary communication with the cloud configuration system 102, reserving wireless as a backup. Alternatively, the one or more BMS controllers 103 may be configured to switch between wired and wireless connections based on availability and network conditions, ensuring consistent connectivity and operational reliability. Yet in another example, the one or more BMS controllers 103 may be communicatively coupled with the cloud configuration system 102 using any known configurations that are compatible to establish such communication. To establish such wireless connectivity, the one or more BMS controllers (103) may include inherent Wi-Fi and Bluetooth Low Energy (BLE) chips. It may be noted here that the cloud configuration platform 102A of the cloud configuration system 102 may extend the capabilities of a Bluetooth-based platform (not shown) designed for, but not limited to, desktop or laptop, enabling seamless integration between the BMS controllers and the cloud environment. In other words, the cloud configuration platform may be enabled with Bluetooth functionality. Thus, the BLE chip facilitates efficient short-range communication with the cloud configuration system 102, allowing for device detection and identification. This enables the cloud configuration platform 102A to automatically discover and interact with multiple BMS controllers, allowing for the simultaneous search, identification, and configuration of multiple BMS controllers, further enhancing flexibility and ease of deployment within the building.
[0025] Furthermore, each of the one or more BMS controllers 103 may have a communication interface (not shown) to facilitate the connection of the respective BMS controller to the cloud configuration system 102 and a BMS interface (not shown) to facilitate the connection of each of the one or more BMS controllers 103 to a corresponding subsystem of the building.
[0026] Further, the system 100 may include a plurality of subsystems 104-1 to 104-N on-premises of the building. The one or more BMS controllers 103 may be communicatively and operably coupled to the plurality of building subsystems 104-1 to 104-N using a communication network. As elucidated previously, in an actual implementation, a single BMS controller may control or monitor multiple subsystems, or each BMS controller may control or monitor a corresponding subsystem. The present disclosure is not limited to these examples. The communication network may include, but not limited to, analog, digital or protocol-based communication network. In an example, the protocol-based communication network comprises a Modbus format, a Building Automation and Control networks (BACNet) format, a Process Field Bus (ProfiBus) format, and/or any other suitable network protocol or combinations thereof.
[0027] Further, the system 100 may include a database storage 105 that may be virtually hosted on the cloud-based sever 100 and may be accessible by the cloud configuration system 102. In an example, the database storage 105 may be a database local to the cloud-based server 101 or may be provided as a database stored on another server remote from the cloud-based server (101). The database storage 105 may store data that is either received, stored, or generated as a result of functions implemented by a system 100. It may be further noted that the data may be utilized by the system 100 for performing various functions of the system 100. The database 105 may be configured to store and organize registry files corresponding to subsystems, mappings of the BMS controllers and the subsystems, and associated configurations; and log all additions, changes, and errors occurred during the configuration.
[0028] FIG. 2 illustrates a block diagram representation of cloud configuration platform 102A in accordance with another embodiment of the present disclosure. In the present disclosure, the cloud configuration platform 102A is implemented on the cloud configuration system 102 in a software manner. The cloud configuration system 102 may logically divide the cloud configuration platform 102A into a space identification module 102A-1, controller selection module 102A-2, subsystem identification module 102A-3, input configuration module 102A-4, output configuration module 102A-5, file generation module 102A-6, processing module 102A-7, sending module 102A-8 and new subsystem addition module 102A-9. It may be noted here that modules disclosed herein may be established as executable instructions execution of which cause the one or more processors of the cloud-based server 101 to implement the respective functionality corresponding to the modules of the cloud configuration platform 102. The modules may be stored in a memory of the cloud-based server 102.
[0029] The one or more processors may be implemented as a dedicated processor(s), a shared processor, or a plurality of individual processor(s), some of which may be shared. Among other capabilities, the processor may fetch and execute instructions stored in the memory. The memory may be coupled to and accessible by the one or more processors. The memory may be a read-only memory (read-only memory, ROM) or another type of static storage device that can store static information and instructions, or may be a random access memory (random access memory, RAM) or another type of dynamic storage device that can store information and instructions, or may be an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a compact disc read-only memory (compact disc read-only memory, CD-ROM) or another optical disk storage, an optical disc storage (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, and the like), or a disk storage medium or another magnetic storage device, or any other medium capable of carrying or storing desired program code in a form of instructions or a data structure and capable of being accessed by a computer. This application not limited thereto.
[0030] Further, the cloud configuration platform 102A may facilitate interactive communication between the modules 102A-1 to 102A-9. A manager (may also be referred to as administrator or technician) who is authorized to configure the one or more BMS controllers 103 may utilize the cloud configuration platform 102A to configure the one or more BMS controllers 103 to control or monitor the subsystems of the building. The manager may access the cloud configuration platform 102A via a web-based interface on, but not limited to, a laptop or desktop, by navigating to the platform’s URL using a web browser or via a mobile application (app) on mobile devices, specifically designed for interacting with the cloud platform’s services or via a desktop application, which provides a dedicated interface for cloud interaction. This application not limited thereto. The manager may access the cloud configuration platform 102A via an interface on a manager-device 106 communicatively coupled to the cloud-based server 101 using a wired or wireless network, the device 106 may be, but not limited to, a laptop, a smartphone, a tablet, or a desktop computer.
[0031] Referring to FIG. 2, the space identification module 102A-1 may be configured to enable a manager of the building to define building-related information comprising building names, number of floors, units and zones. Prior to this, the cloud configuration platform 102A may allow the manager to define one or more organizations whose buildings include subsystems that require control or monitoring by the one or more BMS controllers 103. It may be noted that, in some implementations, a dedicated module (not shown) may be provided for managing organization-related information.
[0032] Further, the controller selection module 102A-2 may be configured to enable the manager to select a BMS controller from the one or more BMS controllers. To select the BMS controller from the one or more BMS controllers 103 may include displaying the one or more BMS controllers communicatively coupled or paired by the manager to the cloud configuration platform 102A and along with their respective unique identifier, for example, MAC address and name.
[0033] Further, the subsystem identification module 102A-3 may be configured to enable the manager to select a subsystem from the plurality of subsystems 104-1 to 104-N to be controlled or monitored by the selected BMS controller. In response to the selection, the subsystem identification module 102A-3 may be configured to retrieve a registry file specific to the selected subsystem from a database 105 of the cloud configuration system 102A. It may be noted here that the subsystem configuration module may be configured to provide a user interface comprising dropdown menus displaying the sub-systems based on respective registry file corresponding to the subsystem stored on the database 105 to streamline the selection of subsystems.
[0034] Furthermore, the input configuration module 102A-4 may be configured to receive a respective input parameter for at least one input port of one or more input ports of the selected BMS controller provided by the manager via the interface and map the respective input parameter to the at least one input port.
[0035] Even further, the output configuration module 102A-5 may be configured to receive a respective output parameter for at least one output port of one or more output ports of the selected BMS controller provided by the manager via the interface and map the respective output parameter to the at least one output port.
[0036] Further, the file generation module 102A-6 may be configured to dynamically generate a machine-readable configuration file based on the received input parameters and the received output parameters and store the machine-readable configuration file in the database 105.
[0037] Furthermore, the processing module 102A-7 may be configured to enable the manager to run a simulation of the generated configuration file to validate the compatibility and functionality of the subsystem when the generated configuration file is executed by the selected BMS controller. In response to running of the simulation, the processing module 102A-7 may be configured to identify errors in the received input parameters or the received output parameters based on the retrieved registry file stored on the database 105 and in response to identification of errors, the processing module 102A-7 may be configured to generate an alert to the manager to correct the errors and enable the manager to re-enter corrected input parameters and/or corrected output parameters when errors are identified, and in response to re-entering, the processing module 102A-7 may be configured to re-map and dynamically update the configuration file based on the corrected input parameters and/or the corrected output parameters and store the updated configuration file in the database 105.
[0038] The sending module 102A-8 may be configured to send the updated configuration file to the selected BMS controller, wherein the selected BMS controller is configured to automatically configure corresponding I/O ports based on the received configuration file.
[0039] In this way, the BMS controller, alternatively referred to as BMS microcontroller, may be configured using cloud configuration platform.
[0040] The cloud configuration platform 102A may further include the new subsystem addition module configured to enable the manager to manually add a new subsystem to the database, wherein to add the new subsystem the manager is to add a registry file specific to the new subsystem. Thus, the module allows the manager to manually add a new subsystem to the database, regardless of its manufacturer. It ensures that the system can accommodate subsystems from new manufacturers or brands by allowing the manager to input a "registry file" specific to the new subsystem. This registry file contains essential information such as the subsystem's type, brand (or manufacturer), model, version, communication protocol, and other relevant parameters required for integration with the cloud configuration system. The ability to add new subsystems from different manufacturers ensures that the building management system remains flexible and adaptable to future expansions or upgrades without being limited to a specific manufacturer or system configuration. It also allows seamless integration of these new subsystems into the existing infrastructure, maintaining operational efficiency and control.
[0041] In accordance with another embodiment of the present disclosure, a method for enabling cloud-based configuration of one or more building management system (BMS) controllers is provided. The method includes hosting a cloud configuration system on a cloud-based server, comprising a cloud configuration platform. The method further includes communicatively coupling one or more BMS controllers to the cloud configuration system. The method further includes defining building-related information, such as building names, number of floors, units, and zones, by a space identification module of the cloud configuration platform. Further, the method includes selecting a BMS controller from the one or more BMS controllers using a controller selection module. The method further includes selecting a subsystem from the plurality of subsystems to be controlled or monitored by the selected BMS controller using a subsystem identification module. Further, the method includes retrieving a registry file specific to the selected subsystem from a database of the cloud configuration system. The method further includes receiving input parameters for input ports and output parameters for output ports of the selected BMS controller and mapping the respective parameters to the respective ports using input and output configuration modules. The method includes dynamically generating a machine-readable configuration file based on the received input and output parameters and storing the configuration file in the database. The method further includes running a processing of the generated configuration file using a processing module to validate its compatibility and functionality with the subsystem. The method includes identifying errors in the input or output parameters based on the retrieved registry file and generating an alert to notify the manager. The method further includes enabling the manager to re-enter the corrected parameters, re-mapping the corrected input parameters and/or corrected output parameters to corresponding I/O ports of the BMS controller and dynamically updating the configuration file based on the corrected parameters. Even further, the method includes sending the updated configuration file to the selected BMS controller, wherein the controller automatically configures its I/O ports based on the received configuration file.
[0042] FIGS. 3-6 depict a flow chart representing the steps involved in a method (300, 400, 500, 600) for enabling cloud-based configuration of one or more building management system (BMS) controllers in accordance with yet another embodiment of the present disclosure.
[0043] The order in which the methods are described is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order to implement the method, or an alternative method. The method may be implemented by processing resources or any computing device(s) through any suitable hardware, non-transitory machine-readable instructions, or combinations thereof.
[0044] It may also be understood that method (300, 400, 500, 600) may be performed by programmed computing devices, such as the cloud configuration platform as depicted in Fig. 1 and Fig. 2. Furthermore, the method (300, 400, 500, 600) may be executed based on instructions stored in a non-transitory computer-readable medium, as will be readily understood. The non-transitory computer-readable medium may include, for example, digital memories, magnetic storage media, such as one or more magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media. While the method (300, 400, 500, 600) are described below with reference to the cloud configuration platform 102A of a system 100 as described above; other suitable systems for the execution of these methods may also be utilized. Additionally, implementation of the method (300, 400, 500, 600) is not limited to such examples.
[0045] At block 302, a cloud configuration system on a cloud-based server, wherein the cloud configuration system comprises a cloud configuration platform may be hosted.
[0046] At block 304, one or more BMS controllers to the cloud configuration system, wherein each of the one or more BMS controllers is operably coupled to a respective subsystem of a plurality of subsystems of a building may be communicatively coupled to the cloud configuration platform.
[0047] At block 306, the manager may be enabled to define building-related information comprising building names, number of floors, units, and zones, via a space identification module of the cloud configuration platform.
[0048] At block 308, the manager may be enabled to select a BMS controller from the one or more BMS controllers by a controller selection module of the cloud configuration platform
[0049] At block 310, the manager may be enabled to select a subsystem from the plurality of subsystems to be controlled or monitored by the selected BMS controller via a subsystem identification module of the cloud configuration platform.
[0050] At block 402, in response to the selection of the subsystem at block 310, a registry file specific to the selected subsystem from a database of the cloud configuration system may be retrieved by the subsystem identification module.
[0051] At block 404, a respective input parameter for at least one input port of one or more input ports of the selected BMS controller provided by the manager may be received via the interface and the respective input parameter may be mapped to the at least one input port.
[0052] At block 406, a respective output parameter for at least one output port of one or more output ports of the selected BMS controller provided by the manager may be received via the interface and the respective output parameter may be mapped to the at least one output port.
[0053] At block 408, a machine-readable configuration file based on the received input parameters and the received output parameters may be generated by a file generation module of the cloud configuration platform.
[0054] At block 502, the generated machine-readable configuration file may be stored in the database of the cloud configuration system.
[0055] At block 504, a simulation of the generated configuration file to validate the compatibility and functionality of the subsystem when the generated configuration file is executed by the selected BMS controller may be run by the manager via a processing module of the cloud configuration platform.
[0056] At block 506, in response to running the simulation, errors in the received input parameters and/or the received output parameters based on the retrieved registry file may be identified by the processing module of the cloud configuration platform.
[0057] At block 508, in response to the identification of the errors, an alert may be generated for displaying the alert to the manager. It may be noted here that in event of no errors, the control may directly implement the block 602 of sending the
[0058] At block 510, in response to the alert, the manager may be enabled to re-enter corrected input parameters and/or corrected output parameters. In response to the re-entry, the corrected input parameters and/or corrected output parameters may be mapped to corresponding I/O ports of the BMS controller and the configuration file based on the corrected input parameters and/or the corrected output parameters may be dynamically updated by the processing module of the cloud configuration platform.
[0059] At block 602, the updated configuration file may be sent to the selected BMS controller by a sending module of the cloud configuration platform, wherein the selected BMS controller is configured to automatically configure corresponding I/O ports based on the received configuration file.
[0060] At block 604, the manager may be enabled to manually add a new subsystem to the database, wherein to add the new subsystem, the manager is required to add a registry file specific to the new subsystem by a new subsystem addition module of the cloud configuration platform.
[0061] Thus, the present subject matter affords several technical advantages including enabling technicians or building managers to access and configure the BMS controllers from any location with an internet connection by leveraging cloud technologies. This eliminates the need for physical presence at the building site, providing greater flexibility and reducing downtime. With the cloud-based platform, the configuration and monitoring of subsystems can be performed remotely, saving time and resources typically spent on travel to the site. The system simplifies the configuration process by providing user-friendly interfaces and step-by-step guidance, making it accessible even to individuals with minimal technical expertise. The platform is designed to reduce complexity, enabling building managers to easily define, configure, and manage various subsystems. Additionally, the cloud configuration system automatically maps parameters and ensures compatibility, minimizing the potential for errors and making the system much easier to operate. The cloud-based platform ensures that subsystems can be quickly configured, tested, and integrated into the building’s operations, enabling buildings to become operational faster and reducing delays in project timelines. With remote access and the ability to configure subsystems without the need for on-site visits, the invention reduces the need for specialized personnel and minimizes the costs associated with physical site visits. Building managers or technicians can manage multiple sites efficiently, leading to substantial savings in labor and travel expenses. Additionally, the automated configuration process minimizes the likelihood of costly mistakes, further contributing to cost savings. Further, the cloud-based platform allows the BMS system to be managed remotely across multiple buildings or locations. This flexibility makes it easier to scale the system as needed, whether adding new subsystems, integrating additional controllers, or expanding to new locations. The platform can accommodate the growing needs of a building or an entire portfolio of properties, ensuring that the system is both adaptable and capable of managing a larger number of subsystems as the infrastructure expands. This scalability ensures that businesses can efficiently manage and operate multiple buildings without the need for a large, on-site workforce.
[0062] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are exemplary and explanatory of the disclosure and are not intended to be restrictive thereof.
[0063] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person skilled in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.
[0064] The figures and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, the order of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts need to be necessarily performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples.
,CLAIMS:1. A system (100) comprising:
a cloud configuration system (102) hosted on a cloud-based server (101) and comprising a cloud configuration platform (102A) accessible by a manager of a building via an interface of a manager-device (106);
a plurality of subsystems (104-1 to 104-N) on-premises of the building; and
one or more building management system (BMS) controllers (103) on-premises of the building, wherein the one or more BMS controllers (103) are communicatively coupled to the cloud configuration system and each of the one or more BMS controllers (103) is communicatively and operably coupled to a respective subsystem of the plurality of subsystems (104-1 to 104-N);
wherein the cloud configuration platform (102A) comprises:
a space identification module (102A-1) configured to enable the manager to:
define building-related information comprising building names, number of floors, units and zones;
a controller selection module (102A-2) configured to enable the manager to:
select a BMS controller from the one or more BMS controllers (103);
a subsystem identification module (102A-3) configured to:
enable the manager to select a subsystem from the plurality of subsystems (104- 1 to 104-N) to be controlled or monitored by the selected BMS controller; and
in response to the selection of the subsystem, retrieve a registry file specific to the selected subsystem from a database (105) of the cloud configuration system (102);
an input configuration module (102A-4) configured to:
receive, from the manager via the interface, a respective input parameter for at least one input port of one or more input ports of the selected BMS controller via an interface and map the respective input parameter to the at least one input port;
an output configuration module (102A-5) configured to:
receive, from the manager via the interface, a respective output parameter for at least one output port of one or more output ports of the selected BMS controller and map the respective output parameter to the at least one output port;
a file generation module (102A-6) configured to:
dynamically generate a machine-readable configuration file based on the received input parameters and the received output parameters and store the machine-readable configuration file in the database;
a processing module (102A-7) configured to:
enable the manager to run a simulation of the generated configuration file to validate the compatibility and functionality of the subsystem when the generated configuration file is executed by the selected BMS controller;
in response to running the simulation, identify errors in the received input parameters or the received output parameters based on the retrieved registry file;
in response to the identification of errors, generate an alert to the manager to correct the errors; and
enable the manager to re-enter corrected input parameters and/or corrected output parameters;
in response to the re-entry, re-map the and corrected input parameters and/or corrected output parameters to corresponding I/O ports of the BMS controller and dynamically update the configuration file based on the corrected input parameters and/or the corrected output parameters; and
a sending module (102A-8) configured to:
send the updated configuration file to the selected BMS controller, wherein the selected BMS controller is configured to automatically configure the corresponding I/O ports based on the received configuration file.
2. The system as claimed in claim 1, wherein each controller of the one or more BMS controllers (103) comprises a Wi-Fi chip or Bluetooth chip.
3. The system as claimed in claim 1, wherein the cloud configuration platform (102A) is enabled with Bluetooth functionality.
4. The system as claimed in claim 1, further comprises:
a new subsystem addition module (102A-9) configured to enable the manager to manually add a new subsystem to the database, wherein to add the new subsystem the manager is to add a respective registry file of the new subsystem.
5. The system as claimed in claim 1, wherein the subsystem configuration module is configured to provide a user interface comprising dropdown menus to streamline the selection of subsystems.
6. The system as claimed in claim 1, wherein the database is configured to:
store and organize registry files corresponding to subsystems, mappings of the BMS controllers and the subsystems, and associated configurations; and
log all additions, changes, and errors occurred during the configuration.
7. The system as claimed in claim 1, wherein the registry file comprises information such as type, brand, model, communication protocol and version specific to the subsystem.
8. The system as claimed in claim 1, wherein to select the subsystem is to select the subsystem based on type, brand, model and version of the subsystem.
9. The system as claimed in claim 1, wherein to select the BMS controller is to select the BMS controller based on media access control (MAC) address corresponding to the BMS controller.
10. A method (300, 400, 500, 600) for enabling cloud-based configuration of one or more building management system (BMS) controllers, the method comprising:
hosting (302) a cloud configuration system on a cloud-based server, wherein the cloud configuration system comprises a cloud configuration platform accessible by a manager of a building via an interface on a manager-device;
communicatively coupling (304) one or more BMS controllers on-premises of the building to the cloud configuration system, wherein each of the one or more BMS controllers is operably coupled to a respective subsystem of a plurality of subsystems on-premises of the building;
enabling (306) the manager to define building-related information comprising building names, number of floors, units, and zones, via a space identification module of the cloud configuration platform;
enabling (308) the manager to select a BMS controller from the one or more BMS controllers via a controller selection module of the cloud configuration platform;
enabling (310) the manager to select a subsystem from the plurality of subsystems to be controlled or monitored by the selected BMS controller via a subsystem identification module of the cloud configuration platform;
retrieving (402), by the subsystem identification module, a registry file specific to the selected subsystem from a database of the cloud configuration system;
receiving (404), by an input configuration module of the cloud configuration platform, a respective input parameter for at least one input port of one or more input ports of the selected BMS controller and mapping the respective input parameter to the at least one input port;
receiving (406), by an output configuration module of the cloud configuration platform, a respective output parameter for at least one output port of one or more output ports of the selected BMS controller and mapping the respective output parameter to the at least one output port;
dynamically generating (408) a machine-readable configuration file based on the received input parameters and the received output parameters by a file generation module of the cloud configuration platform;
storing (502) the machine-readable configuration file in the database of the cloud configuration system;
running (504), by a processing module of the cloud configuration platform, a processing of the generated configuration file to validate the compatibility and functionality of the subsystem when the generated configuration file is executed by the selected BMS controller;
identifying (506), by the processing module, errors in the received input parameters and/or the received output parameters based on the retrieved registry file;
generating (508) an alert to the manager to correct the errors identified in the received input parameters and/or the received output parameters;
enabling (510) the manager to re-enter corrected input parameters and/or output parameters;
re-mapping (510) the corrected input parameters and/or corrected output parameters to corresponding I/O ports of the BMS controller and dynamically updating the configuration file based on the corrected input parameters and/or the corrected output parameters; and
sending (602), by a sending module of the cloud configuration platform, the updated configuration file to the selected BMS controller, wherein the selected BMS controller is configured to automatically configure corresponding I/O ports based on the received configuration file.
11. The method as claimed in claim 10, further comprising:
enabling (604) the manager, by a new subsystem addition module of the cloud configuration platform, to manually add a new subsystem to the database, wherein to add the new subsystem, the manager is required to add a respective registry file of the new subsystem.
Dated this 19th day of December 2024
Signature
Gokul Nataraj E
Patent Agent (IN/PA-5309)
Agent for the Applicant
| # | Name | Date |
|---|---|---|
| 1 | 202321079741-STATEMENT OF UNDERTAKING (FORM 3) [23-11-2023(online)].pdf | 2023-11-23 |
| 2 | 202321079741-PROVISIONAL SPECIFICATION [23-11-2023(online)].pdf | 2023-11-23 |
| 3 | 202321079741-FORM FOR STARTUP [23-11-2023(online)].pdf | 2023-11-23 |
| 4 | 202321079741-FORM FOR SMALL ENTITY(FORM-28) [23-11-2023(online)].pdf | 2023-11-23 |
| 5 | 202321079741-FORM 1 [23-11-2023(online)].pdf | 2023-11-23 |
| 6 | 202321079741-EVIDENCE FOR REGISTRATION UNDER SSI(FORM-28) [23-11-2023(online)].pdf | 2023-11-23 |
| 7 | 202321079741-EVIDENCE FOR REGISTRATION UNDER SSI [23-11-2023(online)].pdf | 2023-11-23 |
| 8 | 202321079741-Proof of Right [19-01-2024(online)].pdf | 2024-01-19 |
| 9 | 202321079741-FORM-26 [31-01-2024(online)].pdf | 2024-01-31 |
| 10 | 202321079741-PostDating-(21-11-2024)-(E-6-290-2024-MUM).pdf | 2024-11-21 |
| 11 | 202321079741-APPLICATIONFORPOSTDATING [21-11-2024(online)].pdf | 2024-11-21 |
| 12 | 202321079741-FORM-26 [29-11-2024(online)].pdf | 2024-11-29 |
| 13 | 202321079741-Power of Attorney [19-12-2024(online)].pdf | 2024-12-19 |
| 14 | 202321079741-FORM-26 [19-12-2024(online)].pdf | 2024-12-19 |
| 15 | 202321079741-DRAWING [19-12-2024(online)].pdf | 2024-12-19 |
| 16 | 202321079741-Covering Letter [19-12-2024(online)].pdf | 2024-12-19 |
| 17 | 202321079741-CORRESPONDENCE-OTHERS [19-12-2024(online)].pdf | 2024-12-19 |
| 18 | 202321079741-COMPLETE SPECIFICATION [19-12-2024(online)].pdf | 2024-12-19 |
| 19 | 202321079741-FORM-9 [20-12-2024(online)].pdf | 2024-12-20 |
| 20 | 202321079741-FORM-8 [20-12-2024(online)].pdf | 2024-12-20 |
| 21 | 202321079741-STARTUP [23-12-2024(online)].pdf | 2024-12-23 |
| 22 | 202321079741-FORM28 [23-12-2024(online)].pdf | 2024-12-23 |
| 23 | 202321079741-FORM 18A [23-12-2024(online)].pdf | 2024-12-23 |
| 24 | Abstract.jpg | 2025-01-16 |
| 25 | 202321079741-FER.pdf | 2025-11-20 |
| 26 | 202321079741-FORM-26 [21-11-2025(online)].pdf | 2025-11-21 |
| 27 | 202321079741-FORM 3 [21-11-2025(online)].pdf | 2025-11-21 |
| 1 | 202321079741_SearchStrategyNew_E_SearchHistoryE_20-11-2025.pdf |