Building Automation Scenario Library Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing automated electrical systems for buildings are difficult to configure and reconfigure, especially when they require multiple interrelated actions and various types of addressable elements, due to complex combinations of input and output units and lack of user familiarity with software features.

Innovation Solution

A processing unit with a library of use-case scenarios that includes definitions of addressable elements, interrelated actions, and an interaction interface for easy configuration and updating, allowing users to select and configure scenarios through a user-friendly interface, such as a web-based or mobile app interface, enabling the creation of complex scenarios involving nonlinear processing and internal variables.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a software interface is used to allow installers to program the operation of automation systems, then installers can experiment with a wide range of available functions, but various intrinsic features of the software are rarely used due to lack of familiarity and complex combinations of elements required to perform specific functions

Engineering Contradiction:
Improverange of available functionsVSAvoiduser familiarity and configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent segments the configuration process into predefined action templates that separate the complex logic (handled by the system) from the simple selection (handled by the user). Each action template represents a discrete, pre-configured behavior that can be independently selected and configured, breaking down the overwhelming complexity of programming individual input-output relationships into manageable, pre-digested units.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer of predefined action templates that mediate between the user's simple selection and the system's complex execution. These templates act as intermediaries that translate high-level user intentions into detailed control logic, eliminating the need for users to directly program complex relationships between input units, output units, and control elements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple interrelated actions and various types of addressable elements are required to configure complex scenarios, then the system can achieve sophisticated automation functions, but the configuration becomes difficult and time-consuming

Engineering Contradiction:
Improvecomplex automation functionsVSAvoidconfiguration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring action templates with all the necessary logic, parameters, and relationships between elements before the user needs them. Complex scenarios are broken down into pre-packaged action templates that already contain the sophisticated automation logic, so users don't need to spend time configuring these complex relationships from scratch - they only need to select and instantiate the pre-prepared templates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges multiple interrelated actions and various types of addressable elements into unified action templates. Each template combines multiple input units, output units, control elements, and logic relationships into a single configurable unit, allowing users to achieve sophisticated automation functions by selecting and configuring fewer integrated templates rather than manually coordinating multiple separate elements.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If a library of use-case scenarios is provided, then scenarios can be easily configured and reused, but the library requires updates and extensions that may compromise software integrity

Engineering Contradiction:
Improvescenario configurabilityVSAvoidsoftware integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the software architecture into a stable core layer (containing fundamental system logic and integrity constraints) and an extensible template layer (containing configurable action templates). This segmentation allows the library of use-case scenarios to be extended and updated in the template layer without compromising the integrity of the core system layer. New templates can be added, modified, or removed independently while the core software remains protected and unchanged.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP3352422B1Configuration of programmed behavior in electrical system
Publication Date: 2020.04.08 NIKO NV
  • EP3352422B1 patent drawingFigure 1~2
  • EP3352422B1 patent drawingFigure 3
  • EP3352422B1 patent drawingFigure 4~5

AI summary

The invention relates to a processing unit (100) for controlling a programmable electrical system (99) of a building that comprises a plurality of addressable elements (111,112). The processing unit (100) comprises a storage medium (2) comprising a library of use-case scenarios, wherein each use-case scenario comprises a definition of a plurality of types of elements required for the use-case scenario. Each use-case scenario also comprises a plurality of interrelated actions defining behaviors of elements of these types, in which each action defines a behavior of at least one of the elements that acts as an output node as a function of a status of at least one of the elements that act as an input node. The processing unit (100) further comprises an interaction interface (7) for presenting an overview of at least a part of the use-case scenarios in the library to a user and for enabling the user to select one of the presented use-case scenarios. For each use-case scenario, the plurality of types of elements comprises at least two of a virtual input node, a virtual output node and/or a type of addressable element (111,112) of said programmable electrical system (99) that is capable of acting as an input node and/or an output node.