AutomationML Device Type Integration via Template Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In industrial automation environments, the existing methods for processing engineering objects face challenges in dynamically integrating new device types due to differences in modeling principles between engineering and runtime systems, leading to high maintainability and efficiency issues during data exchange using AutomationML.
Innovation Solution
A method and system that involve obtaining a data file with engineering objects, identifying the device type, determining necessary transformations based on metadata, and transforming the device type from one data format to another, allowing for dynamic adaptation of object hierarchies and data formats, such as between AutomationML and engineering project data formats.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the entire object model is modified to support a new device type during import/export operations, then the device can be integrated into the system, but the maintainability of the system deteriorates and update efforts increase
Solution Approach 1:
The patent segments the object model into template objects and instance objects. Template objects define the structure and behavior for device types, while instance objects represent specific device instances. This segmentation allows new device types to be added by creating new template objects without modifying the existing object model structure, thereby maintaining system maintainability while improving adaptability.
Solution Approach 2:
The patent creates a universal import/export mechanism that works with multiple device types through a common template object structure. The template objects provide a universal interface that can represent different device types (e.g., S120 Drive, motors, encoders) without requiring separate import/export logic for each device type, thus improving adaptability without increasing system complexity.
2Adaptability or versatility
If the object model is modified each time a new device type is supported, then the device compatibility improves, but the time and efforts required for system updates increase
Solution Approach 1:
The patent performs preliminary action by pre-defining template objects that represent device types and their hierarchical structures. These template objects are prepared in advance and stored in the system. When a new device type needs to be supported, the system can quickly instantiate new template objects based on the existing structure rather than modifying the entire object model, significantly reducing update time while maintaining device compatibility.
Solution Approach 2:
The patent uses copying by creating new template objects as copies or extensions of existing template object structures. Instead of modifying the core object model, new device types are added by copying the template structure and adapting it to the specific device requirements. This approach enables rapid integration of new device types without time-consuming model modifications.
3Manufacturing precision
If device-specific modeling principles are applied in the engineering system, then the device representation accuracy improves, but the complexity of the object model increases
Solution Approach 1:
The patent applies local quality by allowing template objects to have device-specific properties and hierarchical structures tailored to each device type's requirements. For example, drive devices can have specific properties for motor connections, while encoder devices have properties for feedback signals. This enables accurate device representation without imposing a complex unified structure on the entire object model, as each template object maintains appropriate complexity only where needed.
Data Source
AI summary
The present disclosure provides a method and system for processing engineering objects in an industrial automation environment. The method includes obtaining a first data file from a user device. The first data file includes one or more engineering objects in a first data format. Further, the method includes identifying a device type associated with the one or more engineering objects in the first data file. The method includes determining one or more transformations associated with the identified device type based on a metadata file stored in a database. Furthermore, the method includes transforming the identified device type to a second data format based on the determined one or more transformations. Additionally, the method includes generating a second data file including the transformed device type in the second data format on a graphical user interface.