Building Equipment Data-Point Binding for Automated Function Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current building equipment planning and engineering processes are inefficient due to the lack of a model that automatically matches functions and devices, requiring high manual effort and being communication technology-dependent.

Innovation Solution

A machine-readable provider and consumer model is processed to describe data-point interactions, allowing functions and devices to be automatically matched and deployed during commissioning, with connection groups calculated based on affected contexts, using a common semantic naming model and communication technology-independent interaction layer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If manual mapping and binding of data-points is performed for each instance, then functions and devices can be interconnected, but planning and engineering effort increases significantly

Engineering Contradiction:
Improveautomated matching of functions and devicesVSAvoidplanning and engineering time
Core Design Contradiction:
Extent of automationVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-defining function templates with standardized data-point interfaces before actual building equipment planning. These templates include pre-configured provider and consumer models that automatically match with devices based on semantic naming conventions, eliminating the need for manual data-point mapping during commissioning and significantly reducing planning time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating reusable function templates that can be instantiated multiple times across different building equipment. Instead of manually configuring each function-instance separately, the system copies the standardized template structure and automatically adapts it to specific devices through automated matching based on semantic names and data-point interfaces

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If conventional KNX application architecture with group address mapping is used, then functions can be bound to devices, but the binding is limited to execution level and not communication technology independent

Engineering Contradiction:
Improvecommunication technology independenceVSAvoidbinding architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies universality by designing a communication technology-independent binding architecture that works across multiple protocols (KNX, BACnet, Modbus, etc.). The function templates and device matching mechanism are protocol-agnostic, using standardized semantic naming conventions that allow the same binding logic to operate regardless of the underlying communication technology, thereby achieving multi-functionality across different building automation standards

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

Solution Approach 2:

The patent introduces an intermediary layer in the form of standardized function templates that act as mediators between devices and the control system. These templates provide a protocol-independent interface that translates between various communication technologies and the unified function model, simplifying the binding architecture by decoupling device-specific protocols from the universal function binding mechanism

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If runtime models like OPC UA platforms are used, then multiple communication paradigms are supported, but no common model describes how functions and devices interwork on a template basis

Engineering Contradiction:
Improvesupport for multiple communication paradigmsVSAvoidease of deploying standardized function templates
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent applies segmentation by dividing the building automation system into distinct, independently configurable segments: device models with standardized interfaces, function templates with provider/consumer data-point models, and connection groups. This segmentation allows each component to be developed, validated, and deployed separately while maintaining standardized interconnection points, making it easier to deploy standardized templates across multiple communication paradigms without requiring a monolithic runtime model

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20240402670A1Methods And Platforms For Planning And Operating Building Equipment
Publication Date: 2024.12.05 SIEMENS SCHWEIZ AG
  • US20240402670A1 patent drawing
  • US20240402670A1 patent drawing
  • US20240402670A1 patent drawing

AI summary

Various embodiments include methods for planning and operating building equipment. An example method includes: processing a machine-readable provider and consumer model describing data-points modelling a provision or consumption of data by functions; and exchanging data through connections with other data-points modelling a provision or consumption of data by devices of the building equipment.