Engineering Tool Asset History Extraction From Operation Logs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing asset management systems require manual input or limited automation for generating change history information, necessitating user interaction to identify changed portions in file assets.

Innovation Solution

An asset management system that automatically generates summary information of changes by analyzing operation logs from engineering tools, extracting relevant changes, and storing them in a database, along with detailed information for easy retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual input or limited automation is used for generating change history information, then user control and verification are maintained, but user workload and time consumption increase

Engineering Contradiction:
Improveaccuracy of change history informationVSAvoidtime for generating change history information
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically capturing operation history information from engineering tool logs before the user needs to review changes. The asset management device proactively extracts change content from operation logs and prepares summary information in advance, eliminating the need for users to manually track changes after they occur.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by automatically generating change history information without requiring user intervention. The asset management device independently extracts operation history from engineering tool logs, identifies changed portions, and creates summary information automatically, allowing the system to serve itself rather than relying on manual user input.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If automatic generation of change history information is implemented, then user workload is reduced, but the ability to readily recognize changed portions deteriorates

Engineering Contradiction:
Improveease of generating change history informationVSAvoiddifficulty of recognizing changed portions
Core Design Contradiction:
Ease of operationVSDifficulty of detecting and measuring

Solution Approach 1:

The system extracts only the essential change information from operation logs, separating relevant change content from unnecessary operational details. The asset management device identifies and extracts specific changed portions by analyzing operation history information, pulling out only the critical elements that users need to recognize changes without being overwhelmed by raw log data.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies local quality by providing detailed change information specifically where needed rather than uniformly processing all operation data. The asset management device focuses extraction on portions of operation logs that contain actual changes to file assets, applying different processing quality to different segments of the operation history based on their relevance to change detection.

Inventive Principle:
Principle #3Local quality

3Loss of information

If detailed operation history information is stored, then complete change tracking is achieved, but data storage requirements and processing complexity increase

Engineering Contradiction:
Improvecompleteness of change informationVSAvoidcomplexity of processing operation history information
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system extracts only the necessary change-related information from comprehensive operation logs, removing redundant operational details. The asset management device selectively extracts change content by analyzing operation history information and identifying only the portions that represent actual file asset changes, thereby maintaining information completeness while reducing data volume.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system segments operation history information into distinct change events and non-change operations. The asset management device divides the continuous operation log into discrete change portions, separating actual file asset modifications from other operational activities, which simplifies processing while preserving complete change tracking information.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12481623B2Recording medium, asset management device, learning device, asset management system, and asset management method
Publication Date: 2025.11.25 MITSUBISHI ELECTRIC CORP
  • US12481623B2 patent drawing
  • US12481623B2 patent drawing
  • US12481623B2 patent drawing

AI summary

An asset management program causes a computer to function as an acquirer that acquires operation history information indicating a history of operations on a file asset in an engineering tool from an operation log file generated in the engineering tool, and an extractor that extracts summary information indicating a summary of content of a change made to the file asset from the operation history information. The asset management program controls the computer such that the extractor causes the summary information to be stored into a database.