Building Management Virtualization for Legacy BMS Cloud Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Building energy management systems (BMS) face inefficiencies due to poor capture of usage requirements at startup and suboptimal configurations from changes in occupancy patterns and infrastructure modifications, with 'pure play' cloud solutions causing redundant investments, complex migration, and costly integrations with legacy systems.

Innovation Solution

A hybrid cloud/on-premise model using GeoBMS, which integrates with existing BMS through a cloud-based middle layer, providing unified APIs for remote access, data consistency, and multi-stakeholder access, while protecting existing investments and avoiding operational disruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If pure play cloud BMS solutions are implemented, then remote access and system reconfiguration capabilities are improved, but existing on-premise BMS investments become redundant and migration complexity increases

Engineering Contradiction:
Improveremote access capabilityVSAvoidmigration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a cloud-based intermediary layer that sits between existing on-premise BMS systems and end users. This intermediary provides remote access and reconfiguration capabilities without requiring complete system replacement. The cloud layer translates and communicates with legacy protocols, enabling modern functionality while preserving existing investments.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is segmented into distinct layers: the existing on-premise BMS infrastructure remains intact while a separate cloud-based management layer is added. This segmentation allows independent operation of legacy systems and modern cloud services, enabling gradual migration and avoiding forced complete replacement.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If pure play cloud BMS solutions are implemented, then scalability is improved, but integration costs with legacy building subsystems increase significantly

Engineering Contradiction:
Improvesystem scalabilityVSAvoidintegration cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The cloud-based BMS acts as an intermediary that handles integrations with legacy building subsystems through standardized interfaces. This mediator layer absorbs the complexity and cost of proprietary protocol integrations, while exposing simplified standardized APIs to cloud services, thereby enabling scalability without proportional integration cost increases.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements universal integration capabilities through standardized protocols and interfaces at the cloud layer. A single integration architecture serves multiple building subsystems and functions, eliminating the need for separate integration efforts for each legacy system and enabling scalable deployment across diverse environments.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If manual weaning of building subsystems from on-premise BMS is performed, then cloud migration is achieved, but system downtime risks and operational disruptions increase

Engineering Contradiction:
Improvecloud migration capabilityVSAvoidoperational continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by establishing cloud-based connectivity and testing communication pathways before actual migration activities. Configuration changes and data synchronization are pre-planned and validated in the cloud environment before being applied to production systems, minimizing unexpected disruptions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The architecture maintains continuous operation of building subsystems throughout the migration process. The on-premise BMS continues to control building equipment while the cloud layer gradually assumes management functions. This parallel operation ensures uninterrupted building services and allows incremental migration without forced downtime.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS11782406B2Virtualizing building management systems
Publication Date: 2023.10.10 CANDELA IOT INC
  • US11782406B2 patent drawing
  • US11782406B2 patent drawing
  • US11782406B2 patent drawing

AI summary

Methods and apparati for virtualizing building management systems. An apparatus embodiment comprises a first API for accessing on-premise building management systems; coupled to the first API, a virtualization engine configured to receive and deploy commands to the first API; and coupled to the virtualization engine, a second API configured to receive and deploy commands to the virtualization engine.