Smart Gateway Device for BMS Integration of Third-Party HVAC Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Building management systems (BMS) face challenges in interfacing with third-party devices that use proprietary communication protocols, leading to increased commissioning, maintenance, and monitoring times due to incompatibility with the main BMS network, requiring costly software and hardware for integration and often providing limited functionality.
Innovation Solution
A smart gateway device is introduced to facilitate communication between BMS networks and non-compatible third-party networks by detecting physical devices, generating virtual devices, and polling data points to expose them to the BMS network, enabling seamless integration and monitoring without additional programming or configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If interface devices are provided for communicating with the BMS network, then connectivity is achieved, but device complexity and setup time increase
Solution Approach 1:
The gateway device performs automatic protocol detection and configuration, eliminating the need for manual setup and reducing complexity. The system self-configures by detecting the proprietary protocol being used and automatically establishing the appropriate translation rules, thereby achieving connectivity without increasing operational complexity.
Solution Approach 2:
The gateway is pre-configured with support for multiple proprietary protocols and automatically performs the necessary configuration actions before actual device communication begins. This preliminary preparation eliminates complex setup requirements during deployment.
2Reliability
If additional software is developed to communicate with third-party networks, then device monitoring capability is improved, but development cost and time increase
Solution Approach 1:
The gateway device is designed with universal protocol support, enabling it to communicate with multiple different proprietary protocols through a single platform. This multi-functionality eliminates the need to develop separate software for each third-party device, reducing development costs while maintaining comprehensive monitoring capability.
Solution Approach 2:
Instead of developing custom software for each proprietary protocol, the gateway creates virtual representations (copies) of the third-party devices that conform to standard BMS protocols. This allows the BMS to monitor devices through standardized interfaces without requiring proprietary software development.
3Ease of operation
If technicians manually interface with third-party communication networks, then device access is achieved, but commissioning and maintenance time increase
Solution Approach 1:
The gateway serves as an automatic intermediary that handles all communication translation between the BMS network and third-party devices. This eliminates the need for technicians to manually interface with proprietary networks, achieving device access while dramatically reducing commissioning and maintenance time.
Solution Approach 2:
The gateway automatically detects the protocol being used by third-party devices and adjusts its translation rules accordingly, providing real-time feedback adaptation. This automated feedback mechanism eliminates manual configuration time while ensuring proper device access.
Data Source
AI summary
A smart gateway device for a first network associated with a building management system (BMS) is configured to discover a physical device and generate a new virtual device responsive to a determination that a device identifier of the physical device does not match any device identifiers in a virtual device registry. The virtual device registry provides mapping between the new virtual device and the physical device. One or more data points of the new virtual device correspond to one or more data points of the physical device. The smart gateway device is configured to receive data values for the one or more data points of the physical device and update the one or more data points of the new virtual device with the data values for the one or more data points of the physical device. The virtual device is configured to represent the physical device on the first network.