Dynamic Order Process Creation Using Modular Task Building Blocks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for managing orders, such as pre-packaged applications and legacy systems, lack flexibility and efficiency in handling complex processes, particularly in industries like telecommunications, where manual intervention and product variations require frequent process changes, leading to high order fallout rates and customer dissatisfaction.

Innovation Solution

An order management system dynamically creates processes from pre-defined tasks when an order is received, integrating disparate systems and enabling both manual and automatic provisioning through an order manager, process creation module, and database that uses building blocks to define products and link them to necessary tasks, allowing for easy addition or alteration of products without extensive reprogramming.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If pre-packaged applications are used to automate processes, then implementation cost and time are reduced, but flexibility and adaptability to specific product needs deteriorate

Engineering Contradiction:
Improveimplementation timeVSAvoidprocess flexibility
Core Design Contradiction:
Loss of timeVSAdaptability or versatility

Solution Approach 1:

The system dynamically creates and modifies processes at runtime based on product configurations and order requirements. Process definitions are not fixed but can be adjusted on-the-fly to accommodate specific needs, allowing the system to maintain both quick implementation and high adaptability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system uses configurable parameters and variables to define process behavior. By changing parameters rather than reprogramming entire processes, the system can quickly adapt to different products and requirements while maintaining a standardized process framework that is easy to implement.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If legacy systems are used to provide custom processes, then process customization is improved, but implementation cost and time increase

Engineering Contradiction:
Improveprocess customizationVSAvoidimplementation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system breaks down complex processes into discrete, modular tasks that can be independently configured and combined. This segmentation allows custom processes to be built by assembling pre-defined task modules rather than programming entire processes from scratch, reducing implementation time while maintaining customization capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses a universal task framework that can handle multiple types of processes through a common structure. The same task templates and process patterns can be applied across different products and industries, reducing the time needed to implement custom processes while maintaining flexibility through parameter configuration.

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

3Stability of the object's composition

If hard-wired solutions are used in pre-packaged applications, then system stability is improved, but ability to reflect process changes deteriorates

Engineering Contradiction:
Improvesystem stabilityVSAvoidprocess changeability
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system maintains stable core process frameworks while allowing dynamic configuration of specific process parameters and flows. The underlying system structure remains stable and well-defined, but the actual process execution can be flexibly adjusted through configuration files, databases, or runtime parameters without requiring reprogramming.

Inventive Principle:
Principle #15Dynamics

4Ease of manufacture

If multiple separate applications are used to handle different process steps, then functional specialization is improved, but system integration and communication efficiency deteriorate

Engineering Contradiction:
Improvefunctional specializationVSAvoidinformation reentry
Core Design Contradiction:
Ease of manufactureVSLoss of information

Solution Approach 1:

The system merges multiple specialized applications into a unified process orchestration platform that maintains the functional capabilities of each component while adding a central coordination layer. This layer manages data flow and communication between specialized modules, eliminating the need for manual information reentry while preserving functional specialization.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system introduces an intermediary process management layer that acts as a mediator between specialized applications. This intermediary handles data translation, validation, and routing between different functional modules, ensuring seamless communication and eliminating information silos while allowing each module to remain highly specialized.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7469219B2Order management system
Publication Date: 2008.12.23 ACCENTURE GLOBAL SERVICES LTD
  • US7469219B2 patent drawing
  • US7469219B2 patent drawing
  • US7469219B2 patent drawing

AI summary

A system for managing orders for products, including goods and services, which dynamically creates processes for providing those products has been developed. This order management system creates the processes from pre-defined tasks when the order is received. By operating in this manner, the order management system dynamically creates processes, even for new or changed products and services, and provides a foundation for the process automation and the human workflow that may be required to provision an order. The order management system may include a database, which includes a data structure that enables the functionality of the order manager and stores information relating to products, building blocks, and tasks, including the relationships among the products, building blocks, and tasks. The data structure generally includes a task entity class, a building block entity class, and an order mapping entity class.