Dynamic Workflow Engine for Loan Processing Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of mortgage loan origination processes, involving geographically dispersed participants with varying technology levels and regulatory entities, poses challenges for automating workflows due to non-deterministic sequences of activities and the need for flexible integration across multiple systems and geographies.

Innovation Solution

A dynamic workflow system that decomposes top-level activities into child activities, using an activity engine to manage and perform these tasks recursively, allowing for flexible sequencing and user interaction, with rules evaluated dynamically to optimize resource usage and accommodate changing contexts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If traditional workflow automation methods are used, then automation benefits can be achieved in static environments, but the system cannot handle non-deterministic sequences of activities in complex loan processing environments

Engineering Contradiction:
Improveworkflow automationVSAvoidflexibility to accommodate changing contexts
Core Design Contradiction:
Extent of automationVSAdaptability or versatility

Solution Approach 1:

The patent applies dynamics by transforming the workflow system from a static, predetermined sequence model to a dynamic, context-driven model. The system continuously evaluates contextual parameters (loan type, underwriting criteria, investor requirements) and adapts the workflow sequence in real-time, allowing activities to be added, removed, or reordered based on current conditions rather than following a fixed path defined at design time.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the fundamental parameter of workflow determination from static configuration to dynamic evaluation. Instead of hardcoding activity sequences, the system uses contextual parameters (loan characteristics, regulatory requirements, participant availability) to dynamically determine which activities to perform and in what order, enabling the same system to handle diverse loan scenarios with varying sequences.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If a monolithic client-server application is used, then deployment and operational simplicity is achieved, but the system cannot integrate across multiple geographies, enterprises, and systems

Engineering Contradiction:
Improvedeployment simplicityVSAvoidintegration capability across distributed environments
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments the monolithic workflow system into distributed, independent workflow engines that can operate across multiple enterprises and geographies. Each participant (lender, broker, appraiser) can have their own workflow engine instance, which communicates through standardized interfaces, allowing the system to scale across distributed environments while maintaining operational simplicity through modular deployment.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal workflow engine that can function across diverse environments (different enterprises, geographies, systems) by implementing a common framework that handles context evaluation and activity orchestration. This universal engine can adapt to specific local requirements while maintaining consistent core functionality, enabling integration across distributed participants without requiring proprietary customizations at each site.

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

3Extent of automation

If proprietary patterns are imposed on the environment, then automation benefits are achieved in controlled environments, but no single entity has enough control to impose patterns in complex multi-enterprise environments

Engineering Contradiction:
Improveworkflow automationVSAvoidapplicability across multiple enterprises
Core Design Contradiction:
Extent of automationVSAdaptability or versatility

Solution Approach 1:

The patent introduces a contextual parameter evaluation mechanism as an intermediary between the workflow engine and individual enterprises. This mediator layer handles the complexity of coordinating across multiple enterprises by evaluating contextual parameters and determining appropriate activities without requiring any single enterprise to impose proprietary patterns on others. The intermediary enables automation while respecting the autonomy of each participant.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If deterministic sequencing is assumed at the outset, then optimization can be made, but flexibility to later incorporate new activities and flows is lost

Engineering Contradiction:
Improveprocessing efficiencyVSAvoidflexibility to incorporate new activities
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent makes the workflow sequence dynamic rather than fixed, allowing the system to optimize processing efficiency by evaluating contextual parameters and determining the most efficient activity sequence at runtime based on current conditions, while simultaneously maintaining flexibility to incorporate new activities and flows as business requirements evolve without reprogramming the entire workflow.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7853464B2Dynamic workflow architectures for loan processing
Publication Date: 2010.12.14 CORELOGIC INC
  • US7853464B2 patent drawing
  • US7853464B2 patent drawing
  • US7853464B2 patent drawing

AI summary

Systems and methods are provided for processing loan applications in dynamic workflows. In a preferred embodiment, a system calls an activity engine with a top-level activity for processing a work-item, e.g., a loan application. The activity engine decomposes the top-level activity into child activities and lower-level child activities, and recursively calls itself to process the child activities until all constituent child activities have been preformed, thus performing the original top-level activity. In the preferred embodiment, each activity, work-item, user, event and role has associated rules, wherein an event represents a change in state of an activity and a role represents a class of users of the system having shared attributes. The evaluation of the associated rules dynamically creates the flow of activities, thereby creating a dynamic workflow.