Unified Data Pattern for Version and Audit Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data management systems face inefficiencies and inconsistencies when maintaining reference and transactional information due to the need for multiple data patterns to perform various functions, leading to confusion and inefficiency.

Innovation Solution

A data pattern comprising an identity table, a version table, and an audit table is used to store and manage information, with the version table tracking versions of the information and the audit table recording modifications and effectiveness periods, allowing for efficient tracking and retrieval of information over time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple different data patterns are used to store information for each specific function (auditing, versioning, effectiveness tracking), then each function can be performed independently, but the system becomes complex and inconsistent due to maintaining the same reference information in multiple data patterns

Engineering Contradiction:
Improvefunctional capabilityVSAvoiddata pattern complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple separate data patterns (auditing pattern, versioning pattern, effectiveness pattern) into a single unified data pattern. This unified pattern uses a single table structure that can simultaneously store reference information, audit information, version information, and effectiveness information, eliminating the need to maintain multiple separate data patterns for the same reference information.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The unified data pattern is designed to be universal and multi-functional, capable of performing auditing, versioning, effectiveness tracking, and other data management functions within a single table structure. This eliminates the need for separate specialized data patterns for each function.

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

2Adaptability or versatility

If multiple data patterns are maintained for the same reference information to support different functions, then each function can be performed, but confusion and inefficiency arise from maintaining consistency across multiple patterns

Engineering Contradiction:
Improvefunctional supportVSAvoiddata maintenance ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

By combining multiple data patterns into one unified pattern, the patent eliminates the operational complexity of maintaining consistency across multiple separate patterns. The unified pattern allows data to be maintained in a single location, reducing confusion and improving ease of operation.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If separate data patterns are used for auditing, versioning, and effectiveness tracking, then each function can be implemented independently, but the system loses efficiency and generates inconsistency

Engineering Contradiction:
Improvedata consistencyVSAvoiddata management efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The unified data pattern merges auditing, versioning, and effectiveness tracking into a single table structure, ensuring data consistency by maintaining all information in one place rather than across multiple separate patterns. This eliminates inconsistency while improving efficiency.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The unified data pattern provides universal support for multiple functions (auditing, versioning, effectiveness tracking) within a single table, improving productivity by eliminating the need to query and maintain multiple separate patterns while ensuring data consistency across all functions.

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

Data Source

PatentUS8782070B2Data pattern for storing information, including associated version and audit information for use in data management
Publication Date: 2014.07.15 ORACLE INT CORP
  • US8782070B2 patent drawing
  • US8782070B2 patent drawing
  • US8782070B2 patent drawing

AI summary

Information is stored in a data pattern. The data pattern includes an identity table, a version table that includes at least one reference to the identity table, and an audit table that includes at least one reference to the version table. The identity table stores information identifying the information. The version table stores version information identifying one or more versions of the information identified in the identity table. The audit table stores audit information identifying when each of the one or more versions of the information was modified. The audit table may also store effectiveness information identifying when each of the one or more versions of the information is in effect.