Device management system

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing device management systems face inefficiencies in data access due to flat data structures, requiring extensive searching for desired data, which slows down processing and increases computational load.

Innovation Solution

Implementing a hierarchical device data model that organizes data into components, functions, and specifications, allowing for quicker data access and reducing search complexity by structuring data in a way that entities can be searched first, followed by associated data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a flat data structure is used to store device data, then the system is simple to implement, but data access time increases due to the need to search all data

Engineering Contradiction:
Improvedata structure complexityVSAvoiddata access time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent segments device data into a hierarchical structure with device-level information and component-level information. This segmentation allows the system to first locate the relevant device category (reducing search space) and then access specific component data, thereby resolving the contradiction between structural simplicity and access efficiency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to the data structure, organizing data from device level to component level. This dimensional change transforms the flat search problem into a two-stage process: first locate the device category, then access the specific component, significantly improving access time while maintaining implementation simplicity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Device complexity

If all device data is stored at the same level in a flat structure, then the data model is simple, but computational load increases when searching for specific data

Engineering Contradiction:
Improvedata model structureVSAvoidcomputational load
Core Design Contradiction:
Device complexityVSPower

Solution Approach 1:

The patent segments the data model into device-level and component-level hierarchies. This segmentation reduces computational load by limiting the search scope to relevant device categories first, then accessing specific components only when needed, rather than searching through all device data uniformly.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a hierarchical dimension to the data model, creating layers from device to component. This dimensional organization reduces computational complexity by enabling targeted searches within specific hierarchical levels, avoiding the need to process all data at a single flat level.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Speed

If a hierarchical data structure is implemented to organize data by components and functions, then data access speed improves, but the data structure becomes more complex

Engineering Contradiction:
Improvedata access speedVSAvoiddata structure complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent segments device data into a hierarchical structure with device-level and component-level information. This segmentation improves data access speed by enabling targeted searches within specific hierarchical levels, while the segmentation itself provides a systematic organization that manages complexity through clear structural boundaries.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to organize data from device level to component level. This dimensional change significantly improves access speed by reducing the search space, while the hierarchical organization manages complexity through systematic layering and clear relationships between levels.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentEP3982050B1Device management system
Publication Date: 2024.07.24 DAIKIN INDUSTRIES LTD
  • EP3982050B1 patent drawingFigure 1
  • EP3982050B1 patent drawingFigure 2
  • EP3982050B1 patent drawingFigure 3

AI summary

A device management system (1) includes a storage unit (41) and a processing unit (43). The storage unit (41) stores data of a device (11, 12) as a device data model having a hierarchical structure. The device data model is a data model in which at least one of information relating to a component of the device (11, 12), information relating to a function of the device (11, 12), and information relating to a specification of the device (11, 12) is associated with the device (11, 12). In response to a processing request from an external program, the processing unit (43) reads or rewrites the data stored as the device data model in the storage unit (41).