Building Automation Data Exchange for Cross-Domain Planning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current building construction and automation systems lack integration across different domains, leading to independent planning and engineering of subsystems, resulting in inefficiencies and the need for redundant data entry and information reuse challenges.
Innovation Solution
A facility system utilizing a common data exchange platform for planning and automation of buildings, enabling integration of automation and non-automation devices, and supporting cross-domain integration through a modular, extendable structure with a graph database, model control unit, and data exchange platform for efficient data management and collaboration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If independent planning and engineering of subsystems is performed, then each subsystem can be planned and executed separately, but information must be entered again and again leading to redundancy and inefficiency
Solution Approach 1:
The patent merges previously separate planning processes into a unified facility system where automation devices and non-automation devices are planned together. The common data exchange platform consolidates information from multiple sources (architects, building planners, electrical installers, system integrators, panel builders, IT experts) into a single integrated model, eliminating redundant data entry while maintaining independent planning capabilities through modular device configurations.
Solution Approach 2:
The facility system creates a universal planning platform that handles multiple device types and domains (automation and non-automation) through a common interface. The system allows different experts to work with the same data structure using their own specialized tools and methods, while the underlying unified model ensures information consistency and reusability across all subsystems.
2Adaptability or versatility
If separate planning of automation and non-automation domains is performed, then domain-specific expertise can be applied, but integration complexity increases
Solution Approach 1:
The facility system acts as an intermediary layer between domain-specific planning processes and the final integrated building system. It provides a common data exchange platform that translates and harmonizes information from different domains (automation, electrical infrastructure, HVAC, etc.) into a unified facility model, reducing integration complexity while preserving domain-specific planning flexibility through standardized interfaces.
Solution Approach 2:
The system segments the building into discrete devices and functional units that can be planned and configured independently within the unified facility system. Each device (whether automation or non-automation) is represented as a separate entity with standardized attributes, allowing domain-specific expertise to be applied to individual segments while the overall system integration is managed through the common platform.
3Adaptability or versatility
If multiple independent systems are used for different building aspects, then specialized functionality is achieved, but data reuse becomes difficult
Solution Approach 1:
The facility system creates a universal data model that can represent multiple device types and domains within a single integrated structure. Information entered for one purpose (e.g., architectural layout) is automatically available for other purposes (e.g., automation planning, electrical distribution, commissioning), enabling maximum information reuse while maintaining specialized functionality through device-specific configurations and attributes.
Data Source
Figure 1
Figure 2
AI summary
A facility system for automation of a building is provided, with: a structure module, configured to provide a modular extendable virtual structure of an architectural representation of at least one building; an automation functionality module, configured to provide modular extendable functionalities associated with physical devices spatial linked with the virtual structure of the building; an extendable device module, configured to provide specification and configuration data of virtual devices corresponding to the physical devices of the building associated to the functionality module and spatial linked to the structure module; an input interface, configured to receive data related to at least one of the modules of the facility system; and a data exchange platform, configured to link the modules of the facility system and the input interface.