Model Transformation Engine for Industrial Data Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current information integration technologies face challenges in efficiently mapping and exchanging model elements between heterogeneous data specifications, particularly in the Engineering Asset Management domain, due to interoperability issues between different standards like ISO 15926 and MIMOSA, which require manual adjustments and are time-consuming and non-reusable.

Innovation Solution

A computer-implemented method and system for generating a transformation engine using a model transformation user interface that allows users to visually define and modify element terms and relationships across multiple hierarchically linked layers, enabling the transformation of model elements from one information system to another, with the ability to create reusable transformation specifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual mapping and transformation methods are used between different data specifications, then data exchange between heterogeneous systems is achieved, but the process becomes time-consuming and non-reusable

Engineering Contradiction:
Improveinteroperability between data specificationsVSAvoidtime required for data transformation
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent pre-defines transformation rules and mappings between different data specifications (ISO 15926, MIMOSA, IEC 61360) in a transformation engine. These transformations are prepared in advance and stored as reusable templates, eliminating the need for manual mapping during actual data exchange operations. The system automatically applies these pre-configured transformations when data needs to be exchanged between heterogeneous systems.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates reusable transformation templates that can be copied and applied multiple times across different data exchange scenarios. Once a transformation rule is defined between two data specifications, it can be reused indefinitely for transforming similar data structures, replacing repetitive manual mapping efforts with automated template-based transformations.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If manual adjustments are made for data integration between different standards, then interoperability is achieved, but the complexity and effort increase significantly

Engineering Contradiction:
Improvedata integration capabilityVSAvoidintegration system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a transformation engine as an intermediary component that mediates between different data specifications. This engine contains pre-configured knowledge about multiple standards (ISO 15926, MIMOSA, IEC 61360) and automatically performs the complex mapping operations. Users interact with a simplified interface while the transformation engine handles the underlying complexity of reconciling different data models and specifications.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The transformation engine is designed to support multiple data specifications and transformation scenarios through a single unified system. It can transform data between ISO 15926 and MIMOSA, between IEC 61360 and other standards, and supports various transformation modes (one-to-one, one-to-many, many-to-one). This multi-functional approach eliminates the need for separate manual integration processes for each standard combination.

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

3Productivity

If reusable transformation specifications are implemented, then transformation efficiency improves, but the initial setup and configuration effort increases

Engineering Contradiction:
Improvetransformation speedVSAvoidinitial configuration time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs the configuration work upfront by pre-defining transformation rules, data mappings, and transformation logic in the transformation engine. Although this initial setup requires time and effort, it enables rapid, automated transformations thereafter. The one-time configuration investment pays off through repeated use of the same transformation specifications across multiple data exchange operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Once transformation specifications are created, they can be copied and reused across multiple projects and scenarios. The system stores transformation templates that can be instantiated repeatedly without requiring reconfiguration, thereby amortizing the initial setup effort across numerous transformations and achieving high productivity.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10445707B2Method and system for information integration in industrial systems
Publication Date: 2019.10.15 UNIVERSITY OF ADELAIDE
  • US10445707B2 patent drawing
  • US10445707B2 patent drawing
  • US10445707B2 patent drawing

AI summary

A computational method for performing a data transformation process for use in Engineering Asset Management on an industrial scale is described, The method and associated integration environment includes a transformation engine or module to map model elements and data items from a first information system, for example a procurement and construction database that records the thousands of individual components used to construct an industrial site, to a second information system. Such as an operation and maintenance database. The method uses a model transformation user interface using hierarchically linked layers to allow users to create, view and modify the transformation specification, as well as element terms and element relationships which define a transformation specification, without having to write the underlying code that performs the transformation.