AAS Data Mapping for Unified Multi-Manufacturer Asset Collection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data collection systems face challenges in storing semi-structured AAS data from various manufacturers due to mismatched field names between AAS data and database fields, preventing unified data collection across different equipment and facilities.

Innovation Solution

A data collection system with a receiving module for semi-structured data, a database, an information storage module for storage positions, and a registration module that writes data based on storage position information, utilizing semantic IDs and a mapping processor to map AAS data into a structured database format, enabling comprehensive data management and remote control of assets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If AAS data from different manufacturers is collected, then data coverage and versatility are improved, but data storage becomes difficult due to format mismatches

Engineering Contradiction:
Improvedata coverageVSAvoiddata storage complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a mapping processor as an intermediary component between the data receiver and the database. This mapping processor contains mapping information that translates AAS data field names into corresponding database field names, enabling seamless data storage without requiring changes to the database structure or the source data format.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent separates the data storage function into two independent parts: the database maintains its fixed structure while the mapping processor handles the translation of AAS data fields. This segmentation allows the database to remain simple and efficient while the mapping processor manages the complexity of format conversion.

Inventive Principle:
Principle #1Segmentation

2Productivity

If a fixed database structure is used, then data storage efficiency is improved, but semi-structured AAS data cannot be stored due to field name mismatches

Engineering Contradiction:
Improvedata storage efficiencyVSAvoiddata compatibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The mapping processor serves as a mediator that translates between the fixed database structure and the semi-structured AAS data format. It uses stored mapping information to automatically match AAS data fields with database fields, enabling efficient storage of diverse data formats without compromising database performance.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the parameter of field name mapping by storing mapping information that associates AAS data field names with database field names. This parameter change enables the system to handle variable AAS data formats while maintaining a fixed, efficient database structure.

Inventive Principle:
Principle #35Parameter changes

3Stability of the object's composition

If manual data format unification is implemented, then data standardization is improved, but system complexity and processing time increase

Engineering Contradiction:
Improvedata standardizationVSAvoidprocessing complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-storing mapping information that defines the correspondence between AAS data field names and database field names. This mapping information is prepared in advance and automatically applied during data reception, eliminating the need for manual format unification processes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The mapping processor performs automatic field name translation using pre-stored mapping information, enabling the system to self-service the data standardization task without requiring manual intervention. The system automatically matches AAS data fields with database fields based on the stored mapping relationships.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240152118A1Data collection system and remote control system
Publication Date: 2024.05.09 KK TOSHIBA
  • US20240152118A1 patent drawing
  • US20240152118A1 patent drawing
  • US20240152118A1 patent drawing

AI summary

According to one embodiment, a data collection system includes a receiving module configured to receive semi-structured data including first data of a first level and a plurality of second data of a second level, the first data including a plurality of the second data, wherein a plurality of second identification information are respectively set for a plurality of the second data, a database, an information storage module configured to store storage position information indicating storage positions of a plurality of the second identification information in the database, and a registration module configured to write a plurality of the second data to the database based on the storage position information.