Analysis Software Managing System for Component Proposal

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data analysis software systems rely heavily on analysis history, making it inefficient and costly to propose data analysis components at the time of system introduction or start of operation, as the effectiveness of proposed components is unknown until actual execution and confirmation by users.

Innovation Solution

An analysis software managing system that generates analysis relationship information linking analysis target data from multiple systems and specifies combinations of analysis components based on this information, enabling proposal of data analysis components irrespective of implementation history.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If analysis software systems rely on analysis history to propose data analysis components, then the reliability of proposed components is improved, but the productivity of system introduction and initial operation is deteriorated

Engineering Contradiction:
Improvereliability of proposed analysis componentsVSAvoidproductivity of system introduction
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by collecting data relationships from multiple predetermined systems before analysis is actually needed. The analysis relationship information is generated in advance, storing the structural relationships between data items across different systems. This preliminary collection and organization of relationship data enables the system to propose analysis components immediately upon startup without requiring historical analysis records, thus resolving the contradiction between reliability and initial productivity.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If analysis software systems wait for implementation history to accumulate before proposing data analysis components, then the reliability of proposals is improved, but the time required for initial operation is increased

Engineering Contradiction:
Improvereliability of analysis component proposalsVSAvoidtime for initial operation
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by collecting data relationships from multiple predetermined systems before analysis is actually needed. The analysis relationship information is generated in advance, storing the structural relationships between data items across different systems. This preliminary collection and organization of relationship data enables the system to propose analysis components immediately upon startup without requiring historical analysis records, thus resolving the contradiction between reliability and initial productivity.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If analysis software systems use analysis history for component proposals, then the accuracy of proposals is improved, but the complexity of the system is increased

Engineering Contradiction:
Improveaccuracy of analysis component proposalsVSAvoidcomplexity of analysis software system
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system extracts only the essential relationship information between data items from multiple predetermined systems, storing this extracted structure in analysis relationship information. Instead of maintaining and processing complete historical analysis records, the system extracts and stores only the structural relationships between data items, which are sufficient for proposing analysis components. This extraction approach reduces system complexity while maintaining proposal accuracy.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary actions by collecting data relationships from multiple predetermined systems before analysis is actually needed. The analysis relationship information is generated in advance, storing the structural relationships between data items across different systems. This preliminary collection and organization of relationship data enables the system to propose analysis components immediately upon startup without requiring historical analysis records, thus resolving the contradiction between reliability and initial productivity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11016758B2Analysis software managing system and analysis software managing method
Publication Date: 2021.05.25 HITACHI LTD
  • US11016758B2 patent drawing
  • US11016758B2 patent drawing
  • US11016758B2 patent drawing

AI summary

Proposal of data analysis components is enabled to be performed irrespective of the quantity of an implementation history of data analysis, and thus efficiency and cost reduction of production of software for data analysis are promoted. A data utilization platform server 101 is configured to includes a arithmetic device 112 which executes processing of generating analysis relationship information prescribing linkage between analysis target data and an analysis component executing analysis processing for the analysis target table on the basis of a relationship among a plurality pieces of the analysis target data collected from a plurality of predetermined systems; and processing of specifying a combination of a plurality of the analysis components available for predetermined data designated as an analysis target by a user on the basis of the analysis relationship information.