Reusable Template Library for Automation Engineering Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current automation systems lack a cross-industry concept for reusing existing technological objects and modules across different domains, leading to increased development costs and inefficiencies in project engineering.

Innovation Solution

A system and method for managing and providing reusable technological objects through a centralized library that allows users to create, store, and update elements as templates, enabling their replication and use in new solutions, with bi-directional connections for automatic updates and user-controlled modifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If existing solutions are reused across different domains, then development costs are reduced, but there is no cross-industry concept available to enable this reuse

Engineering Contradiction:
Improvedevelopment costVSAvoidcross-industry applicability
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal library system that stores technological objects as reusable templates with standardized interfaces and attributes. These templates can be instantiated across different domains (automation, MES, etc.) by simply changing parameters, enabling the same core elements to serve multiple industries and applications without requiring separate development for each domain.

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

2Productivity

If reusable modules are stored in domain-specific libraries, then development efficiency is improved within that domain, but there is no provision for making modifications when using reusable modules

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidmodification capability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system implements dynamic templates where reusable modules are defined with configurable parameters and attributes. When instantiated, these templates can be dynamically modified by adjusting their parameters without affecting the original template. The system maintains a hierarchy between templates and instances, allowing modifications at the instance level while preserving the ability to update all instances when the template changes.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If elements are created from scratch for each project, then complete customization is achieved, but development costs and engineering overhead increase

Engineering Contradiction:
Improvecustomization capabilityVSAvoiddevelopment cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system pre-defines technological objects as templates with standardized structures, attributes, and interfaces before they are needed in specific projects. These templates are created once and stored in a library, then reused across multiple projects through instantiation. This preliminary creation of reusable elements eliminates the need to recreate common components from scratch for each project, significantly reducing development costs while maintaining customization through parameter adjustment.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7418300B2System and method for reusing project engineering data
Publication Date: 2008.08.26 SIEMENS AG
  • US7418300B2 patent drawing
  • US7418300B2 patent drawing
  • US7418300B2 patent drawing

AI summary

The invention relates to a system and a method for managing and/or providing elements, in particular technological objects. The system enables elements, in particular technological objects, to be reused in the development of a project engineering solution. Here, at least one element is created, in particular by a user of the system, with the at least one element serving as a template for the generation of an exemplar as an image or a plurality of exemplars as images of the element. The created elements are stored in a library and an exemplar of a stored element is created, the exemplar being used in the development of a solution, in particular an automation solution.