Modular Object Database for Secure Business Data Linking

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing business modeling and data management systems face challenges in efficiently linking and automating data across different databases, managing complex data structures, and ensuring robust data security, particularly in distributed environments.

Innovation Solution

A modular object database system that fragments business objects into key and value objects, allowing for decentralized storage and management of attributes and methods, with a scalable security concept that ensures data security and enables automated process execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data are stored in different separate databases (product data management systems, product requirement systems, standards information systems), then data can be managed in specialized systems, but linking data between these databases becomes very complex and automation is very complex

Engineering Contradiction:

Improvedata management capabilityVSAvoiddata linking complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple separate databases (product data management, product requirements, standards information) into a single integrated database system. This integration allows data from different domains to be linked through common object references and unique identifiers, eliminating the complexity of inter-database linking while maintaining specialized data management capabilities through structured data organization and access methods

Inventive Principle:

Principle #5Merging (Combining)

2Device complexity

If a monolithic system covers entire subject areas with a common database, then links between data can be produced more easily, but changes to the database are associated with considerable effort

Engineering Contradiction:

Improvedata linking complexityVSAvoiddatabase modification flexibility

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent segments the monolithic database into modular components organized around business objects (products, requirements, standards, processes). Each object type can be independently defined, modified, and managed through standardized interfaces. This segmentation allows easy database changes and additions without requiring comprehensive system redesign, while maintaining efficient data linking through object relationships

Inventive Principle:

Principle #1Segmentation

3Loss of information

If processes are stored in separate databases where they are only documented, then processes can be clearly documented with responsibilities, but processes cannot be run in an automated manner and data flows are difficult to track

Engineering Contradiction:

Improveprocess documentation clarityVSAvoidprocess automation capability

Core Design Contradiction:

Loss of informationVSExtent of automation

Solution Approach 1:

The patent implements self-service automation where business processes are encoded as executable logic within the database system itself. Processes automatically execute based on triggered events and predefined rules, eliminating the need for separate documentation-only storage. The system autonomously tracks data flows, manages responsibilities, and executes process steps while maintaining complete audit trails, thereby achieving both clear documentation and full automation capability

Inventive Principle:

Principle #25Self-service

4Device complexity

If attributes and methods are stored together in objects, then object structure is simple, but data security is compromised in distributed environments

Engineering Contradiction:

Improveobject structure simplicityVSAvoiddata security

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The patent segments object data into separate attributes and methods stored in different locations within the distributed database system. Attributes (data) are stored separately from methods (operations), allowing independent security controls, access permissions, and encryption schemes for each component. This segmentation enables fine-grained security management while maintaining simple object-oriented data modeling and access mechanisms

Inventive Principle:

Principle #1Segmentation

5Ease of operation

If the database management system is implemented as objects in the object database, then handling of the object database is simplified, but traditional centralized security models become inadequate

Engineering Contradiction:

Improvedatabase handling simplicityVSAvoidsecurity model adequacy

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent implements a dynamic security model where security permissions and access controls are associated with individual business objects and can be dynamically assigned and modified. Unlike traditional centralized security models, this approach allows different security policies for different objects, users, and operations, adapting to the distributed object-oriented architecture while maintaining ease of database handling through standardized access mechanisms

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS12530380B2Object database for business modeling with improved data security

Publication Date: 2026.01.20 BIERMANN GERHARD

AI summary

A modular object database for holistic, object-oriented business modeling, in which business data and processes of all types are represented separately in key and value objects, wherein the attributes and methods of the objects are likewise stored separately from one another, and the database management system itself is implemented as objects of the object database, as a result of which simpler handling of the object database and substantially improved data security is achieved overall.