Approval Workflow Engine for Service Procurement Visibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for managing service costs and procurement lack visibility and oversight, particularly in complex scenarios involving multiple service providers and approval layers, leading to inefficiencies and lost savings opportunities.

Innovation Solution

Implementing an approval workflow engine and framework that receives transaction information, applies rules to determine approvers, and facilitates notifications and approvals for timesheets, progress logs, and expenses, allowing for multi-level approvals and post-approval adjustments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If traditional purchasing systems are used for services procurement, then simplicity and ease of operation are maintained, but visibility and oversight of service costs deteriorate

Engineering Contradiction:
Improvevisibility of service costsVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments service procurement into distinct transaction types (timesheets, progress logs, expenses) with specific approval workflows for each. This segmentation allows the system to track and provide visibility into service costs while maintaining manageable complexity through structured categorization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary approval workflow system that mediates between service providers and purchasing departments. This intermediary layer captures and structures service cost information, providing visibility and oversight without requiring complete system redesign.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple service providers and approval layers are involved, then comprehensive oversight is achieved, but routing complexity and processing time increase

Engineering Contradiction:
Improveoversight and approval controlVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements dynamic routing that automatically adjusts approval paths based on transaction attributes, service provider information, and organizational hierarchy. This dynamic approach ensures comprehensive oversight through multiple approval layers when needed while reducing processing time by skipping unnecessary approval steps in simpler cases.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback mechanisms where approval status, routing decisions, and transaction information are continuously tracked and communicated back to all stakeholders. This feedback loop improves reliability by ensuring proper oversight while reducing delays through automated status updates and parallel processing capabilities.

Inventive Principle:
Principle #23Feedback

3Productivity

If manual management of service provider information is used, then system simplicity is maintained, but efficiency and productivity deteriorate

Engineering Contradiction:
Improveprocessing efficiencyVSAvoidautomation level
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The patent enables service providers to self-submit timesheets, progress logs, and expenses directly through the system, eliminating manual data entry and improving productivity. The system automatically routes these submissions through appropriate approval workflows, achieving high automation levels while maintaining ease of use through intuitive interfaces.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical processes of service provider information management with automated electronic workflows. The system automatically captures, routes, approves, and processes service cost transactions, dramatically improving processing efficiency while maintaining simplicity through standardized electronic interfaces.

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

4Adaptability or versatility

If flexible approval routing is implemented, then adaptability to different scenarios is improved, but device complexity increases

Engineering Contradiction:
Improveapproval routing flexibilityVSAvoidworkflow system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal approval workflow engine that handles multiple transaction types (timesheets, progress logs, expenses) and service provider scenarios through a single flexible system. This universal approach provides adaptability to different approval scenarios while managing complexity through standardized processes and interfaces.

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

Solution Approach 2:

The system achieves flexibility through parameter-driven routing where approval paths are dynamically determined by transaction attributes, service provider information, and organizational parameters. By changing parameters rather than restructuring the entire system, the patent provides adaptability to various scenarios while maintaining manageable complexity through consistent underlying architecture.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8412599B2Approval workflow engine for services procurement timesheets, progress logs, and expenses
Publication Date: 2013.04.02 ORACLE INT CORP
  • US8412599B2 patent drawing
  • US8412599B2 patent drawing
  • US8412599B2 patent drawing

AI summary

This disclosure describes, generally, methods and systems for implementing an approval workflow engine and approval framework for timesheets, progress logs, and expenses. The method includes receiving, at an approval engine of an application server, information representing a timesheet, progress log, or expense. The approval engine may apply one or more rules to determine whether the rules are satisfied by corresponding attribute values of attributes for the timesheet, progress log, or expense. Notification may be generated and transmitted to one or more approvers and/or reviewers based on applications of the rules. An indication of approval and/or disapproval may be received from each of the approvers and/or reviewers. Rules may be defined for automatic assignment of multi level approvers, based on specific attributes. An approver may have the option to approve, deny, or push back a transaction. Approvers and submitters can have visibility of the full approval path and current approval status throughout an approval process. In addition, post approval adjustments can be routed for approval based on adjustment approval rules.