Workflow Engine Interoperability via Standardized Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional solutions for automating access and communication between computer systems with compatible and incompatible platforms and protocols are costly and require frequent updates, as they often necessitate customized interfaces that fail to function properly with system changes.

Innovation Solution

A system and method for generating, deploying, and executing workflows that facilitate interoperability between systems with different platforms and protocols without the need for customized interfaces, using a graphical user interface to create and sequence tasks, and dispatching workflow records across networks for execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If customized interfaces are created to interface with incompatible systems, then access to and communication of input information is achieved, but the cost in terms of time, money, and resources increases significantly

Engineering Contradiction:
Improveaccess to input informationVSAvoidcustomized interface
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies universality by creating a standardized interface framework that can work with multiple incompatible systems without requiring customized interfaces for each system. The workflow engine provides universal functionality to access and communicate information across diverse computer systems, eliminating the need for system-specific customized interfaces while maintaining reliable access to input information.

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

Solution Approach 2:

The patent uses an intermediary approach by introducing a standardized interface framework and workflow engine that mediates between the user and incompatible computer systems. This intermediary layer handles the complexity of interfacing with different systems, providing a uniform way to access input information without requiring direct customized interfaces to each incompatible system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If additional customized interfaces are created for newly discovered incompatible systems, then access to additional input information sources is achieved, but the cost and time for creation, testing, implementation and support increases

Engineering Contradiction:
Improveaccess to additional systemsVSAvoidcreation and implementation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The standardized interface framework provides universal adaptability to work with any incompatible computer system through a consistent interface paradigm. When new systems need to be accessed, the framework can accommodate them without requiring complete re-engineering or creation of new customized interfaces, significantly reducing the time and resources needed for adaptation.

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

Solution Approach 2:

The workflow engine provides dynamic adaptability to accommodate new incompatible systems as they are discovered or added. The system can dynamically adjust and configure workflows to access input information from new systems without requiring static, pre-configured customized interfaces for every possible system, reducing implementation time.

Inventive Principle:
Principle #15Dynamics

3Reliability

If customized interfaces are updated to work with system updates, upgrades or modifications, then continued functionality is maintained, but additional expenses of time, money and resources are incurred

Engineering Contradiction:
Improveworkflow functionalityVSAvoidinterface maintenance
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The standardized interface framework maintains workflow functionality across system updates by providing universal interface standards that are less susceptible to breaking changes. When computer systems undergo updates or modifications, the standardized framework can accommodate these changes more easily than customized interfaces, reducing the effort and resources required for maintenance.

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

Solution Approach 2:

The workflow engine acts as an intermediary buffer between the standardized interface framework and the underlying computer systems. When systems undergo updates or modifications, the intermediary layer absorbs and manages these changes, protecting the upper-level workflow logic from direct impact and reducing the complexity of maintaining functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If manual solutions are used to interface with incompatible systems, then access to input information is achieved, but the cost in terms of time and human resources increases

Engineering Contradiction:
Improveinformation transferVSAvoidinformation processing speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The automated workflow engine provides self-service functionality to access and transfer information from incompatible computer systems without requiring manual human intervention. The system automatically executes workflows, retrieves input information, and processes data according to predefined logic, eliminating the need for manual information transfer while maintaining reliability and significantly improving productivity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8726285B2Method and apparatus for triggering workflow deployment and/or execution
Publication Date: 2014.05.13 CIANMBELLA LTD
  • US8726285B2 patent drawing
  • US8726285B2 patent drawing
  • US8726285B2 patent drawing

AI summary

A system and method for triggering deployment of a workflow are provided. The method includes issuing, to a first device (e.g., a server) from application software executing on a second device (e.g., a client computer), an instruction to execute a workflow previously deployed at the first device. The workflow is formed as a function of information associated with a graphical representation of the workflow. The application software may be, for example, software for one or more word-processing, spreadsheet, database, email, instant messenger, presentation, browser, calendar, organizer, media, image-display applications; file management programs and/or operating system shells. Alternatively, the application software may be or include a module associated with such application software. This module may include or be formed as or from one or more plug-ins, add-ons, applets, shared libraries, and/or extensions.