Multi-source Configurator Automates Contract Creation from RFx Documents

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual contract authoring and lack of automation in supplier contract management lead to errors, inconsistencies, and inefficient savings realization due to cumbersome term negotiations and incomplete enforcement in strategic sourcing processes.

Innovation Solution

A multi-source rules-based configurator automates the creation of contract documents from RFx sourcing documents, allowing for inclusion, exclusion, or modification of clauses and text based on predefined rules, reducing manual errors and inconsistencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual contract authoring is used, then flexibility in negotiation is maintained, but errors and inconsistencies increase

Engineering Contradiction:
Improvecontract accuracyVSAvoidmanual authoring effort
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system enables self-service contract generation where the configurator automatically creates contract documents from sourcing documents without requiring manual intervention. The rules-based engine autonomously processes template selection, clause insertion, and document assembly, eliminating manual errors while maintaining operational simplicity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the manual mechanical process of contract authoring with an automated electronic system. The rules-based configurator uses algorithmic logic to process sourcing documents and generate contracts, substituting human manual operations with automated computational processes that eliminate errors and inconsistencies.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If automated contract creation is implemented, then efficiency improves, but complexity of the system increases

Engineering Contradiction:
Improvecontract creation speedVSAvoidconfigurator system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The configurator system is segmented into distinct functional modules: template selection engine, rules-based processing engine, clause insertion module, and document assembly module. Each module handles a specific aspect of contract creation, making the overall complex system manageable through functional decomposition while maintaining high productivity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The rules-based configurator is designed as a universal platform that can process multiple types of sourcing documents and generate various contract templates through a single integrated system. The engine handles template selection, clause management, and document generation universally across different contract types, reducing the need for multiple specialized systems.

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

3Loss of time

If manual term negotiation is performed, then customization is possible, but time consumption increases

Engineering Contradiction:
Improvenegotiation timeVSAvoidterm customization
Core Design Contradiction:
Loss of timeVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary actions by pre-configuring contract templates with standard clauses and terms before the actual contract creation process. The rules-based engine pre-processes sourcing documents to identify applicable clauses, and the template library is pre-populated with negotiated terms, eliminating the need for time-consuming negotiations while maintaining customization through selective clause application.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The configurator enables rapid customization by changing parameters such as clause selection, template variables, and contract terms through automated rule evaluation. Instead of manual negotiation, the system dynamically adjusts contract parameters based on sourcing document content and predefined rules, achieving customization without time loss.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If complete contract enforcement is implemented, then savings realization improves, but operational complexity increases

Engineering Contradiction:
Improvesavings enforcementVSAvoidenforcement mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements feedback mechanisms that automatically track contract compliance and enforce terms through integrated monitoring. The configurator links sourcing requirements to contract clauses and provides automated feedback on compliance status, enabling complete enforcement without manual intervention or complex operational procedures.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10089666B2Multi-source configurator content processing for terms and conditions document to contract creation
Publication Date: 2018.10.02 ORACLE INT CORP
  • US10089666B2 patent drawing
  • US10089666B2 patent drawing
  • US10089666B2 patent drawing

AI summary

An authored contract document can be created based on an existing RFx sourcing document such as a “terms and conditions” document. This RFx sourcing document can be the product of collaboration and editing by unrelated bidders, thus creating bidder-specific RFx documents. The authored contract document can be created using a rules-based multi-source configurator. This multi-source configurator can include in or exclude from the authored contract document clauses or edits that have been made to the RFx document. The multi-source configurator can replace text from the RFx document that is not typically found in or relevant to an authored contract document with contract-specific text that is not typically found in or relevant to an RFx document. The multi-source configurator can add, to the authored contract document, contract-specific text that is not contained within the RFx document.