Fieldbus-to-Cloud Data Structure for Device-Specific Logging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing fieldbus network solutions require extensive device-specific information in the connecting apparatus, leading to complexity and increased effort in data transfer from field devices to the cloud, as they need to manage various device types' addressing and address space occupation.

Innovation Solution

A data structure is implemented using a derived class based on a head class, where devices produce data objects that include both universal head attributes and device-specific additional attributes, shifting the responsibility of data retrieval and compilation to the devices, and the connecting apparatus only converts data into cloud-compatible formats.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the connecting apparatus manages device-specific information for various device types, then data transfer from different devices is enabled, but the complexity of the connecting apparatus increases

Engineering Contradiction:
Improvedata transfer capabilityVSAvoidcomplexity of the connecting apparatus
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The data structure is segmented into a head class containing universal attributes and derived classes containing device-specific attributes. This segmentation allows the connecting apparatus to handle only the universal head class data, while device-specific information is self-contained in the derived classes, reducing the complexity of the connecting apparatus.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The head class acts as an intermediary between the connecting apparatus and various device-specific derived classes. The connecting apparatus communicates only with the standardized head class interface, while the derived classes mediate the device-specific information, eliminating the need for the connecting apparatus to manage complex device-specific information directly.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Quantity of substance

If the connecting apparatus handles device-specific information, then comprehensive data collection is achieved, but the effort in data transfer increases

Engineering Contradiction:
Improvedata collection completenessVSAvoideffort in data transfer
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

Each device instance self-services by automatically generating its own derived class with the appropriate device-specific attributes. This eliminates the need for the connecting apparatus to manually configure or manage device-specific information, significantly reducing the effort and time required for data transfer while maintaining comprehensive data collection.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The derived classes are prepared in advance with all necessary device-specific attributes and configurations before data transfer occurs. This preliminary preparation ensures that when data transfer happens, the connecting apparatus only needs to handle the standardized head class data, reducing the effort and time required during actual data transfer operations.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If a unified data structure is implemented, then data handling is simplified, but flexibility in device-specific parameter logging is reduced

Engineering Contradiction:
Improvedata handling simplicityVSAvoiddevice-specific parameter flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The solution merges the unified head class structure with device-specific derived classes. The head class provides the simplified unified data handling interface, while the derived classes are merged into the head class instances to provide the necessary device-specific parameter flexibility, achieving both simplicity and adaptability simultaneously.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11159340B2Data structure for the transfer of data from a fieldbus network into a cloud
Publication Date: 2021.10.26 ENDRESS HAUSER PROCESS SOLUTIONS AG
  • US11159340B2 patent drawing
  • US11159340B2 patent drawing
  • US11159340B2 patent drawing

AI summary

A fieldbus network is described, which has at least one device as well as a connecting apparatus, wherein the connecting apparatus is designed to transfer data from the fieldbus network into a cloud. Installed in at least one of the devices is a derived class, which is derived from a predetermined head class, wherein head attributes are established by the predetermined head class and additional device specific attributes are established by the derived class, wherein the at least one of the devices is designed based on the derived class to produce a data object for the data transfer to the cloud. The connecting apparatus is designed to receive the data object of the device, to convert at least a part of the data contained in the data object into a format of an interface of the cloud and to write the data into the cloud.