Contract Data Graph Updates for Consistent Metadata Changes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Maintaining consistency and updating contract fields manually is time-consuming, expensive, and error-prone, especially in digitally stored contracts with numerous negotiation points, making it difficult to track and update contract metadata efficiently.
Innovation Solution
A computer-implemented system that automatically updates a digitally stored contract model by creating a graph of answer data and variables, identifying and removing unnecessary edges and nodes based on changes, ensuring consistency and correctness.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual extraction and updating of contract data is performed, then contract metadata can be tracked and updated, but the process becomes expensive, time-consuming, and error-prone
Solution Approach 1:
The patent replaces the manual mechanical process of extracting and updating contract data with an automated computer-implemented system. The system automatically extracts data from contract documents, updates the contract model, and maintains consistency across all fields without human intervention, thereby eliminating time consumption and errors associated with manual processing.
Solution Approach 2:
The contract management system performs self-service by automatically detecting changes in contract fields, identifying affected dependent fields, and updating them accordingly. The system monitors its own data model, detects inconsistencies, and corrects them without requiring external manual intervention, making the process efficient and reliable.
2Adaptability or versatility
If contract fields are manually updated during negotiation, then contract terms can be changed, but consistency among fields becomes difficult to maintain
Solution Approach 1:
The system implements feedback mechanisms by continuously monitoring contract field changes and automatically propagating updates to dependent fields. When a field is modified during negotiation, the system detects the change, identifies which other fields are affected, and updates them accordingly, ensuring the data model remains consistent throughout the negotiation process.
Solution Approach 2:
The contract data model is designed to be dynamic, automatically adapting to changes in contract terms while maintaining internal consistency. The system dynamically identifies relationships between fields and adjusts the data model structure as negotiations progress, allowing flexibility in term changes while preserving data integrity.
3Reliability
If comprehensive tracking of all contract fields is implemented, then consistency can be maintained, but computing resource usage increases
Solution Approach 1:
The system segments the contract data model into distinct fields and relationships, allowing it to track only the specific changes that occur rather than continuously monitoring all fields. By dividing the contract into manageable components and tracking changes at the field level, the system maintains consistency with minimal computing overhead.
Solution Approach 2:
The system performs partial action by updating only the specific fields that are affected by a change rather than reprocessing the entire contract document. When a field changes, the system identifies and updates only the dependent fields that need modification, avoiding unnecessary computing operations while maintaining data consistency.
Data Source
AI summary
The present disclosure provides for a method of automatically updating a digitally stored model of an electronic contract over the lifetime of a contract, including a step of receiving an update to an attribute of a digitally stored contract model. Further, retrieving, from a digital data store, model description data and a plurality of answer values. Based on the model description data and answer values, creating a graph of answer data and variables required in the electronic contract as nodes and edges, where nodes represent the answer data and variables, and edges represent dependencies of the nodes. Next, removing edges that are determined from first variables to second variables that the first variables had been declared as using. From the update to the attributes of the contract model, removing one or more nodes corresponding to the one or more variables that are not directly referenceable by the document.