Automation Module Libraries for Cross-Discipline Configuration Reuse
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing automation systems face challenges in effectively connecting and managing different disciplines, such as IEC programming, visualization, and network configuration, which are independent from each other, leading to inefficiencies in the configuration and development of automation projects.
Innovation Solution
The creation of an automation module that serves as a container for artifacts from various disciplines, allowing for the mapping of physical automation devices, instantiation, and localization, enabling the creation of a shared type object that can be reused across different disciplines and projects, facilitating the connection and interconnection of artifacts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If disciplines are kept independent from each other, then each discipline can be developed and managed separately, but the connection and integration between disciplines becomes difficult and inefficient
Solution Approach 1:
The patent merges multiple independent disciplines (IEC programming, visualization, network configuration, secure programming, motion control) into a unified automation module structure. This allows artifacts from different disciplines to be contained within and connected through a common module framework, resolving the integration difficulty while preserving individual discipline development independence.
Solution Approach 2:
The automation module is designed as a universal container that can hold artifacts from various disciplines simultaneously. This multi-functional structure enables a single module to serve multiple purposes across different engineering disciplines, facilitating seamless connection and integration while maintaining the ability to develop each discipline separately.
2Adaptability or versatility
If automation modules are created with multiple artifacts from various disciplines, then the reuse and standardization of device types is improved, but the initial creation and configuration complexity increases
Solution Approach 1:
The patent applies preliminary action by pre-configuring automation modules with multiple artifacts from various disciplines during the module creation phase. This upfront preparation includes defining the module structure, adding relevant artifacts, and establishing connections between them, so that the module is ready for immediate reuse in different projects without requiring complex configuration each time.
Solution Approach 2:
The patent enables copying of standardized automation module templates that contain pre-defined artifacts and connections. Once a module is created with the necessary artifacts from different disciplines, it can be copied and instantiated multiple times across different projects, reducing the complexity of creating similar modules from scratch each time while maintaining high adaptability and reusability.
3Ease of operation
If disciplines are integrated into a shared container structure, then the interconnection and management of artifacts is simplified, but the initial setup and standardization effort increases
Solution Approach 1:
The shared container structure (automation module) is prepared in advance with predefined slots and connection points for artifacts from different disciplines. This preliminary structuring includes establishing the framework for IEC programming, visualization, network configuration, and other disciplines, so that when artifacts are added later, they can be easily interconnected using the pre-established structure, significantly reducing management complexity.
Data Source
AI summary
A method for configuring an automation system for controlling a process, an automation module, and a computer program product. In the method, a mapping of a physical automation device on a non-instantiated automation module is provided, whereby the non-instantiated automation module specifies a device type and has at least one artifact. Furthermore, the method includes the provision of a non-instantiated automation module in a library and a retrieval of the non-instantiated automation module from the library. Furthermore, the method provides for an instantiation of the automation module and a localization of the instantiated automation modules.