Building Automation System Hierarchical Data Directory

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing building automation systems (BAS) are inflexible and labor-intensive, requiring extensive customization and manual programming for each installation, making them costly and time-consuming, and they struggle with integrating components from different vendors and generations, as well as supporting multiple protocol versions and new devices.

Innovation Solution

A dynamically extensible and automatically configurable BAS architecture that uses a database with a relational directory and a server engine to manage data definitions hierarchically, allowing for integration of legacy and next-generation components, and supporting multiple protocols without manual reconfiguration, through a protocol-agnostic head-end and object-oriented system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If hardwired systems and proprietary communication standards are used, then system robustness and customization for particular installations are improved, but device complexity and installation cost increase

Engineering Contradiction:
Improvesystem robustnessVSAvoidinstallation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal communication interface that can handle multiple communication protocols (BACnet, Modbus, proprietary protocols) through a single standardized gateway architecture. This allows the system to maintain robustness while reducing installation complexity by eliminating the need for separate hardwired connections and custom programming for each protocol type.

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

Solution Approach 2:

The patent introduces communication gateways as intermediary devices that translate between different protocols and the central management system. These gateways absorb the complexity of protocol-specific implementations, allowing the main system to remain simple while still supporting multiple robust communication methods.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If extensive customization and manual programming are performed for each installation, then system adaptability to specific buildings is improved, but installation time and cost increase

Engineering Contradiction:
Improvesystem customizationVSAvoidinstallation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements pre-configured communication templates and automatic device discovery mechanisms that perform preliminary configuration work before installation. The system automatically generates communication parameters and device mappings based on detected device types, eliminating the need for manual programming during installation while maintaining full customization capability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system performs self-configuration by automatically detecting devices on the network, identifying their types and capabilities, and configuring appropriate communication parameters without human intervention. This self-service approach maintains adaptability while dramatically reducing installation time.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If systems integrators are used for manual service and programming, then system integration capability is improved, but expense and operational interruption increase

Engineering Contradiction:
Improveintegration capabilityVSAvoidservice interruption
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements automatic device discovery, identification, and integration mechanisms that eliminate the need for systems integrators to manually configure each device. The system automatically maps devices to appropriate functions and configurations based on detected device characteristics, maintaining integration capability while removing the need for expensive manual service.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent extracts the complex integration logic from manual installer procedures and embeds it within automated system routines. The integration capability is preserved by moving the intelligence from human operators into the system's automatic discovery and configuration mechanisms.

Inventive Principle:
Principle #2Taking out (Extraction)

4Device complexity

If single protocol architectures are used, then system simplicity is improved, but interoperability with multiple protocol versions and vendors is reduced

Engineering Contradiction:
Improvesystem architecture simplicityVSAvoidprotocol interoperability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent segments the communication architecture into protocol-specific gateway modules that can be independently selected and configured. Each gateway handles a specific protocol version or vendor format, while the central system maintains a unified simple interface. This segmentation allows protocol interoperability without complicating the main system architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal gateway architecture that can handle multiple communication protocols through a single standardized interface to the central system. The gateway layer provides multi-functionality, allowing the simple central system to interoperate with various protocol versions and vendor-specific implementations.

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

Data Source

PatentUS7870090B2Building automation system date management
Publication Date: 2011.01.11 TRANE INTERNATIONAL INC
  • US7870090B2 patent drawing
  • US7870090B2 patent drawing
  • US7870090B2 patent drawing

AI summary

A building automation system (BAS). In one embodiment, the BAS comprises a database and a relational directory. The database is adapted to store data definitions. The relational directory includes data definitions for the BAS, stored in the database, and includes a site level, a system level, a device level, and an extension level organized in a hierarchical relationship in the database. In another embodiment, the BAS comprises a database, a relational directory of data definitions for the BAS, and a server engine.