Contract Library Data Structure for Efficient Term Retrieval

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems face inefficiencies in generating contract forms, as they often rely on time-consuming and error-prone manual or keyword-based searches for historical contract data, failing to consider multiple contract classifiers effectively, leading to irrelevant or missing terms in new contracts.

Innovation Solution

A contract library data structure is implemented, organizing contract terms by various classifiers in a hierarchical manner, using nodes and tags to facilitate efficient retrieval and updating of contract terms, allowing for the consideration of multiple classifiers and providing relevant terms through a filter routine and contract term handlers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual or keyword-based searches are used to retrieve historical contract data, then the system is simple to implement, but the process is time-consuming and error-prone

Engineering Contradiction:
Improvecontract term retrieval efficiencyVSAvoidtime for contract form generation
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments contract terms and their classifications into a hierarchical data structure with nodes representing different classification levels. This segmentation allows the system to efficiently retrieve relevant terms by traversing the hierarchy rather than searching through all contract data, thus improving productivity while reducing time loss.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by pre-organizing contract terms into a structured library with multiple classification hierarchies before retrieval is needed. This advance organization enables rapid access to relevant terms during contract form generation, eliminating the need for time-consuming searches at the moment of need.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If traditional database searches are used, then the implementation is straightforward, but multiple contract classifiers cannot be effectively considered

Engineering Contradiction:
Improveability to consider multiple classifiersVSAvoiddata structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies the nested doll principle by creating a hierarchical data structure where nodes contain nested nodes representing different classification levels. Each node can represent a different classifier dimension (e.g., contract type, jurisdiction, party type), allowing multiple classifiers to be considered simultaneously through the nested hierarchy without excessive complexity.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The patent adds another dimension to the data organization by implementing multi-dimensional classification hierarchies. Instead of single-dimensional keyword search, the system organizes terms across multiple classification dimensions (nodes representing different classifier types), enabling versatile term retrieval based on multiple classifiers while managing complexity through structured organization.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Reliability

If keyword-based search is used, then the system is easy to operate, but irrelevant or missing terms are returned

Engineering Contradiction:
Improverelevance of contract termsVSAvoidsimplicity of term retrieval
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies local quality by associating specific contract terms with specific nodes in the hierarchical structure based on their relevant classifications. Each node represents a local context with specific classification characteristics, allowing the system to retrieve terms that are locally relevant to the specific contract situation rather than returning all terms matching a general keyword search, thus improving reliability while maintaining ease of operation through the structured interface.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11762907B2Contract library data structures and uses thereof
Publication Date: 2023.09.19 SAP SE
  • US11762907B2 patent drawing
  • US11762907B2 patent drawing
  • US11762907B2 patent drawing

AI summary

Various examples are directed to systems and methods for generating a contract form using a contract library data structure. A computing device may receive, from a user, a contract form request comprising a set of contract classifiers. The computing device may access a contract library data structure and executes a filter routine to traverse the contract library data structure to identify at least one contract term associated with one or more filter tags corresponding to the set of contract classifiers. The filter routine may return an indication of the first contract term associated with the first node. The computing device may generate a contract form comprising the first contract term.