Component Interaction Metadata for Dynamic System Diagnostics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems lack the ability to automatically provide information on the interaction of components during operation, requiring manual maintenance and making it difficult to diagnose errors and understand system dynamics.

Innovation Solution

A method where metadata, such as macros, is embedded in the source code of system components to store interaction information, allowing a higher-level component to read, evaluate, and display this information dynamically, enabling automatic generation of user interfaces and error diagnosis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If manual maintenance of system interaction information is used, then implementation simplicity is maintained, but information accuracy and automatic adaptation deteriorate

Engineering Contradiction:
Improvecomponent interaction informationVSAvoidsystem configuration complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by embedding metadata about component interactions directly into the source code during the development phase. This metadata is automatically extracted during compilation and made available at runtime, eliminating the need for manual maintenance of interaction information while the compiler handles the complexity of information extraction and validation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service by having components automatically provide their own interaction information through metadata embedded in their source code. Each component's application program self-describes its interactions with other components, eliminating the need for external manual configuration and enabling automatic system understanding.

Inventive Principle:
Principle #25Self-service

2Reliability

If metadata is embedded in source code for automatic information extraction, then information accuracy improves, but compilation and processing complexity increases

Engineering Contradiction:
Improveinteraction information reliabilityVSAvoidprogram compilation ease
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent merges the metadata extraction process with the existing compilation workflow. The compiler is extended to automatically extract metadata from source code comments during the normal compilation process, integrating the complexity of information extraction into the already-necessary compilation step without requiring separate manual processing.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces an intermediary layer of metadata that sits between the source code and the compiled application. This metadata acts as a mediator that the compiler can automatically extract and process, providing reliable interaction information without requiring complex manual analysis of the source code logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If dynamic user interface generation is implemented, then interface adaptability improves, but processing time and computational resources increase

Engineering Contradiction:
Improveuser interface adaptabilityVSAvoidinterface generation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by extracting and storing interaction information metadata during the compilation phase, before runtime. This pre-processing makes the interaction information immediately available when dynamic user interface generation is needed, reducing runtime overhead while maintaining full adaptability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3657276B1System and method for operating a system
Publication Date: 2023.04.19 LENZE AUTOMATION
  • EP3657276B1 patent drawingFigure 1
  • EP3657276B1 patent drawingFigure 2~3

AI summary

Method for operating a system (1) wherein the system (1) comprises: - a plurality of interacting components (2) wherein the method comprises the steps: - storing information (3) concerning the interaction of a respective component (2) with the other components (2) in a respective component (2).