Multi-Functional Component Programming via Function Object Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In industrial automation, multifunctional components require multiple applications for project planning and programming, making it difficult to determine which applications are necessary for processing software objects, especially when components have diverse functionalities and different expansion stages, leading to complexity in infrastructure setup.

Innovation Solution

A method where function objects are stored with project information, assigning applications for creating or editing software objects based on their functionalities, allowing automatic selection and use of necessary applications within the engineering system, without altering existing infrastructure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple applications are used for multifunctional components, then comprehensive processing capability is improved, but infrastructure complexity increases

Engineering Contradiction:
Improveprocessing capabilityVSAvoidinfrastructure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system automatically determines which applications are required for processing software objects without manual intervention. The infrastructure self-configures by analyzing project information and function objects to identify needed applications, eliminating the need for users to manually set up complex multi-application environments.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system pre-determines application requirements by storing function objects with project information that describe required functionalities. Before processing begins, the infrastructure analyzes these stored function objects to identify which applications are needed, preparing the environment in advance rather than requiring manual configuration.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If manual infrastructure setup is required, then application selection accuracy is improved, but time consumption increases

Engineering Contradiction:
Improveapplication selection accuracyVSAvoidsetup time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system uses stored function objects as feedback mechanisms that automatically convey information about required functionalities to the infrastructure. This feedback loop enables the system to automatically determine which applications are needed based on the project's actual requirements, maintaining accuracy while eliminating manual setup time.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The manual mechanical process of selecting and configuring applications is replaced with an automated information processing system. The infrastructure uses stored project information and function objects to automatically determine application requirements, substituting human decision-making with automated analysis that is both accurate and time-efficient.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If all applications are installed, then processing flexibility is improved, but resource consumption increases

Engineering Contradiction:
Improveprocessing flexibilityVSAvoidresource consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

Instead of uniformly installing all applications, the system applies local quality by installing only the specific applications required for each project's functionality. The infrastructure analyzes function objects to determine which applications are locally needed for processing particular software objects, avoiding unnecessary resource consumption while maintaining flexibility.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system dynamically changes the parameter of application installation based on project requirements. Rather than maintaining a static full installation, the infrastructure adjusts which applications are available by determining requirements from stored function objects and project information, optimizing resource usage while preserving processing flexibility when needed.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP2482148B1Method for projecting and/or programming a multi-functional component of an industrial automation assembly
Publication Date: 2018.06.13 SIEMENS AG
  • EP2482148B1 patent drawingFigure 1~2

AI summary

The software objects are assigned to a program, depending on the functionality of the functions contained in an application. The information about the software objects and the functions used in the project are saved along with the project. A particular type and/or stage of development of applications are ruled out, based on the information. The project is carried out using the installed applications, and a respective infrastructure is created using the software object.