Message Broker Architecture for Multi-Site BMS Point Change Alerts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Building management systems (BMS) face challenges in providing real-time information across multiple building sites, as data from one site may not be received and updated in web applications connected to another site, leading to incomplete monitoring of building systems and equipment, and concurrent saving of historical data can cause processing issues.
Innovation Solution
A system that includes a message broker to receive data from a DAQ system, multiple BMS instances connected to the message broker to process and save data, and a web application connected to the message broker to generate notifications of point value changes, allowing for concurrent data updates from multiple sites and efficient resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If data from multiple building sites is processed in a single BMS instance, then real-time monitoring information can be provided, but processing efficiency and system reliability deteriorate due to the large volume of data
Solution Approach 1:
The patent divides the single BMS instance into multiple BMS instances, with each instance responsible for processing data from a specific building site. This segmentation allows parallel processing of data from multiple sites, improving overall processing efficiency while maintaining real-time monitoring capabilities. Each BMS instance handles a subset of the total data load, preventing any single instance from becoming a bottleneck.
Solution Approach 2:
The patent introduces a new dimension of distribution by deploying BMS instances across multiple servers or computing nodes. This dimensional expansion from a single processing unit to a distributed network of processing units enables scalable handling of data from multiple building sites, improving both processing capacity and system reliability.
2Productivity
If multiple BMS instances process data concurrently, then processing capacity increases, but data consistency and coordination become more difficult
Solution Approach 1:
The message broker serves as an intermediary component that coordinates communication between multiple BMS instances and the web application. It manages data flow, ensures proper routing of notifications, and maintains consistency across the distributed system. The message broker abstracts the complexity of inter-instance communication, allowing BMS instances to operate independently while maintaining system-wide data consistency.
Solution Approach 2:
The system implements feedback mechanisms where BMS instances publish point value change notifications to the message broker, which then distributes these notifications to the web application. This feedback loop ensures that all components remain synchronized and that data consistency is maintained across the distributed architecture through continuous information exchange.
3Adaptability or versatility
If web application connects to multiple BMS instances simultaneously, then data from all sites can be monitored, but connection management and notification delivery become complex
Solution Approach 1:
The message broker acts as a central intermediary that the web application connects to once, rather than requiring separate connections to each BMS instance. The broker manages all connections to multiple BMS instances behind the scenes, filtering and routing notifications from relevant instances to the web application. This reduces connection management complexity from O(n) connections to O(1) connection while maintaining multi-site monitoring capability.
4Loss of information
If historical data is saved concurrently by multiple BMS instances, then data collection completeness improves, but processing conflicts and data loss may occur
Solution Approach 1:
Each BMS instance is responsible for saving historical data from its assigned building site independently, segmenting the data storage responsibility. This prevents processing conflicts that would arise from multiple instances simultaneously writing to the same data storage location, while ensuring complete historical data collection across all sites through their respective independent saving operations.
Data Source
AI summary
Methods, devices, and systems for point value change notification are described herein. One system (100) includes a message broker (108) to receive data from a data acquisition (DAQ) system, a first building management system (BMS) instance (104) connected to the message broker (108) to process a first portion of the DAQ data, a second BMS instance (104) connected to the message broker (108) to process a second portion of the DAQ data, and a web application (118) connected to the message broker (108) to generate a notification of a change in point value of a portion of the first portion or the second portion of the DAQ data, where the first BMS instance (104) and the second BMS instance (104) are provisioned with a plurality of computing resources deployed in a computing environment (102, 502) and are ultimately executed on hardware.