Workflow Record for Cross-Platform System Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional solutions for accessing and communicating information between computer systems with compatible and incompatible platforms and protocols require customized interfaces, leading to high costs and inefficiencies due to the need for initial development, support, and updates.

Innovation Solution

A graphical-user interface and system that facilitates the generation, deployment, and execution of workflows without requiring customized interfaces, enabling interoperability between systems with different platforms and protocols, using a workflow record that includes task and sequencing parameters to automate the workflow execution across disparate systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If customized interfaces are developed to interface with incompatible systems, then access to and communication of input information between compatible and incompatible systems is enabled, but the cost in terms of time, money, and resources increases significantly due to initial development, testing, implementation, support, and updates

Engineering Contradiction:
Improveinteroperability between compatible and incompatible systemsVSAvoidcost and resources for customized interface development and maintenance
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a standardized interface that acts as an intermediary layer between compatible and incompatible systems. This standardized interface includes predefined adapters and connectors that can interface with multiple incompatible systems without requiring custom development for each system. The standardized interface translates and mediates communication between different platforms and protocols, enabling interoperability while avoiding the need for expensive customized interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The standardized interface is designed to be universal and multi-functional, capable of interfacing with multiple different incompatible systems through a single platform. The interface supports various protocols and platforms (mainframe, midrange, personal computers, etc.) through standardized adapters, allowing one interface to serve multiple functions across different system types rather than requiring separate customized interfaces for each system.

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

2Ease of operation

If customized interfaces are created for each incompatible system, then access to specific systems is achieved, but the time and resources required to create, test, implement and provide support for each interface version increases

Engineering Contradiction:
Improveaccess to input information on incompatible systemsVSAvoidtime for development, testing, implementation and support of customized interfaces
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent implements predefined adapters and connectors that have been prepared in advance for common incompatible systems. These adapters are pre-configured with the necessary translation rules and communication protocols, so when a new system needs to be accessed, the appropriate pre-built adapter can be quickly deployed without requiring time-consuming custom development and testing cycles.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The standardized interface uses template-based adapter designs that can be quickly replicated and adapted for different systems. Once an adapter for a particular system type is created, it can be copied and modified for similar systems, significantly reducing the time and resources required to create new interface versions compared to developing entirely custom interfaces from scratch.

Inventive Principle:
Principle #26Copying

3Reliability

If customized interfaces are implemented, then initial system integration is achieved, but additional expenses are incurred when new incompatible systems are added or existing systems are updated

Engineering Contradiction:
Improveinitial system integration functionalityVSAvoidflexibility to accommodate system updates and additions
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The standardized interface is designed to be dynamic and adaptable rather than static. The adapter framework allows for easy configuration changes and updates when new systems are added or existing systems are modified. The interface can dynamically adjust to new system requirements by loading appropriate adapters or modifying existing ones, maintaining reliability while accommodating changes without requiring complete reintegration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The interface architecture is segmented into modular adapters and connectors that can be independently updated or replaced. When a new incompatible system is added or an existing one is updated, only the specific adapter for that system needs to be modified or replaced, rather than updating the entire interface. This segmentation maintains system reliability while providing flexibility for future adaptations.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10997531B2System, method and graphical user interface for workflow generation, deployment and/or execution
Publication Date: 2021.05.04 CIANMBELLA LTD
  • US10997531B2 patent drawing
  • US10997531B2 patent drawing
  • US10997531B2 patent drawing

AI summary

A method, system and graphical user interface for generating, deploying and/or executing one or more workflows are provided. The method includes obtaining, via a graphical-user interface, information for executing a plurality of tasks of a workflow, wherein the information defines an abstraction of at least one function of the plurality of tasks, and forming, from the information, a record for executing a workflow, wherein the record is operable to be dispatched to facilitate execution of the workflow.