Digital Object System for Multisystem Data Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Collaborative projects in multisystem environments face challenges such as ineffective data exchange and communication, leading to inefficiencies and system incompatibilities, particularly in managing and tracking services related to physical objects across different systems.

Innovation Solution

The implementation of a digital object system that allows secure data sharing and process visibility by creating a digital object list visible to multiple entities, enabling secure data transmission and management through a digital identifier, which facilitates real-time tracking and service order management across systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data exchange and communication mechanisms are implemented in collaborative projects, then entities can share information and work together, but data loss and processing inefficiency occur due to poor mechanisms

Engineering Contradiction:
Improvedata sharing capabilityVSAvoiddata processing effectiveness
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a digital object as an intermediary entity that mediates data exchange between multiple entities. The digital object contains structured data about physical objects and serves as a common language that different systems can understand and process, eliminating the need for direct complex communication between entities while ensuring data integrity and processing efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If entities adapt a common process for collaborative projects, then collaboration is enabled, but system incompatibilities arise

Engineering Contradiction:
Improvecollaboration capabilityVSAvoidsystem compatibility
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal digital object structure that can represent various physical objects and their attributes in a standardized format. This universal structure allows different systems with varying complexities to interact through a common interface, enabling collaboration without requiring each system to adapt to others' specific formats or processes.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Loss of information

If secure data sharing is implemented across multiple systems, then process visibility is improved, but data transmission complexity increases

Engineering Contradiction:
Improveprocess visibilityVSAvoiddata transmission process
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments data into structured digital objects with defined attributes and relationships. This segmentation allows data to be transmitted in manageable, standardized units that can be easily validated and processed by receiving systems, reducing transmission complexity while maintaining complete process visibility through the structured format.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20230368140A1Data aggregation based on multisystem integration for object collaboration
Publication Date: 2023.11.16 SAP SE
  • US20230368140A1 patent drawing
  • US20230368140A1 patent drawing
  • US20230368140A1 patent drawing

AI summary

In some implementations, supporting system collaboration includes actions of receiving a registration of an account on a system, adding objects to an object list including model information that includes an identifier of a physical object and characteristics of the physical object, publishing the object list to make the object list visible to a plurality of users of the first system, receiving, from one of the plurality of users of the system, a request to export a portion of the object list, conditioning the portion of the object list to be accessible to another system by converting the portion of the object list based on a transmission protocol, formatting the portion of the object list for display on the other system, and packaging the portion of the object list for transmission to the other system, and exporting the portion of the object list to the other system.