Control Object for Distributed Data Ownership Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data administration systems face delays due to centralized monitoring and lack of flexibility in managing data ownership across coupled systems, especially in weakly coupled landscapes where data ownership cannot be easily changed or updated.

Innovation Solution

A method that involves creating a control object to manage data ownership by specifying relationships between model-level and instance-level changes, allowing for flexible assignment of data administration rights and handling unauthorized changes through a control object distributed across systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a centralized entity monitors data ownership among several systems, then data administration control is improved, but communication time and task delay increase

Engineering Contradiction:
Improvedata administration controlVSAvoidcommunication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts the data ownership monitoring function from a centralized entity and embeds it directly into individual systems through control objects. Each system maintains its own control objects that encode data ownership information, eliminating the need for continuous communication with a central monitor while preserving administrative control.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates copies of data ownership control information in the form of control objects that are distributed to individual systems. These control objects contain embedded information about data ownership and relationships between model-level and instance-level changes, allowing systems to operate autonomously without frequent centralized communication.

Inventive Principle:
Principle #26Copying

2Loss of information

If data ownership is assigned to the creator system, then historical tracking is improved, but flexibility to transfer ownership is lost

Engineering Contradiction:
Improvehistorical trackingVSAvoidownership transfer flexibility
Core Design Contradiction:
Loss of informationVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic data ownership through control objects that can be transferred between systems. The control objects contain metadata about the relationship between model-level and instance-level changes, allowing ownership to be flexibly reassigned while maintaining historical information about the object's creation and modification history.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent embeds historical information within the control object structure itself. The control object contains nested information about the data object's creation, ownership history, and the relationships between different levels of changes, preserving historical tracking while enabling flexible ownership transfer.

Inventive Principle:
Principle #7Nested doll (Nesting)

3Adaptability or versatility

If systems are weakly coupled in a landscape arrangement, then system independence is improved, but data administration coordination deteriorates

Engineering Contradiction:
Improvesystem independenceVSAvoiddata administration coordination
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces control objects as intermediaries that carry data administration information between weakly coupled systems. These control objects encode the relationships between model-level and instance-level changes, enabling coordinated data administration across independently operating systems without requiring tight coupling or a central coordinator.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7593916B2Managing data administration
Publication Date: 2009.09.22 SAP SE
  • US7593916B2 patent drawing
  • US7593916B2 patent drawing
  • US7593916B2 patent drawing

AI summary

Data administration may be managed by receiving in a computer system a first input identifying a data object to be assigned to a control object in the computer system. A second input for the control object is received in the computer system. The second input specifies a relationship between 1) model-level changes to the data object, and 2) instance-level changes to the data object. After the first and second inputs are received, the control object is sent to another computer system. The control object may be accessed to determine whether a system is authorized to make an object change. This access can be by the system about to make the change, or by a system that receives the object change from another system.