BEMS Signature Validation for Automatic Reference Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Building Enterprise Management Systems (BEMS) lack a real-time data fetching mechanism to identify changes in signatures and FQRs of HVAC system components, leading to costly and engineering-intensive manual updates, and fail to monitor gateway downtime effectively.
Innovation Solution
A system comprising a processor configured to receive and validate object signatures from a source computing system, generate validated signatures by appending a suffix associated with the current version and configuration, and transmit these to a target computing system, enabling real-time synchronization and automated updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual signature update process is used in conventional BEMS, then system updates can be performed, but the process is costly and engineering-intensive
Solution Approach 1:
The system automatically detects signature changes by comparing object signatures between source and target systems, and self-updates the signature database without requiring manual intervention. The processor autonomously identifies modified objects, retrieves updated signatures, and synchronizes them to the target system.
Solution Approach 2:
The system implements a feedback mechanism where the target system reports signature information back to the source system, which then compares this feedback with its local signature database to detect changes. This closed-loop feedback enables automatic detection and correction of signature discrepancies.
2Loss of information
If no data fetching mechanism is available to identify signature changes, then system complexity is reduced, but real-time synchronization cannot be achieved
Solution Approach 1:
The system introduces an intermediary data fetching mechanism that acts as a bridge between the source and target systems. This intermediary component automatically retrieves signature information, performs comparisons, and facilitates synchronization without requiring complex direct integration between systems.
Solution Approach 2:
The system performs preliminary actions by pre-establishing signature databases at both source and target systems, and by implementing preliminary comparison logic that prepares for change detection. This preliminary setup enables efficient real-time synchronization without requiring complex runtime processing.
3Reliability
If manual signature update process is used, then engineering control is maintained, but time-consuming operations occur
Solution Approach 1:
The system replaces the mechanical manual update process with an automated electronic system. The processor electronically compares signatures, identifies changes, and transfers updated information automatically, eliminating the need for manual engineering operations while maintaining controlled updates through programmed validation rules.
4Adaptability or versatility
If source system version upgrade occurs, then system functionality is improved, but identifier synchronization becomes challenging
Solution Approach 1:
The system implements dynamic signature tracking that adapts to version upgrades. When the source system undergoes version upgrades, the system dynamically updates its signature database and automatically detects changes in object identifiers. The target system similarly adapts by receiving and processing updated signature information, maintaining synchronization across versions.
Data Source
AI summary
A processor is configured to receive an electronic item comprising an object signature and corresponding to a building infrastructure item, such as space, equipment, monitoring point, etc. The processor is configured to validate the object signature, including determining, based on the object signature, a data source associated with the building infrastructure item. For each of the plurality of data objects from the data source, where each data object corresponds to a particular installation of the building infrastructure item, the processor is configured to determine a signature suffix associated with a current version and/or current configuration of the particular installation. The processor is configured to generate a validated object signature, including appending the signature suffix to the object signature. The processor is configured to identify a target computing system and transmit the validated object signature to the target computing system (e.g., in the form of a representational state transfer (REST) message.).


