Universal Computing Elements for Scalable Workflow Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software and business process development paradigms are often rigid, siloed, and difficult to scale, with hardcoded configuration values that make changes slow and expensive, and struggle with real-time data processing and concurrency.

Innovation Solution

The implementation of universal computing elements (UCEs) that comprise an object queue, counters, and functions operating on object parameters, enabling multi-system connectivity and automation through state machines that can transition objects between nodes and handle complex processes with real-time data processing and scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing software systems use hardcoded configuration values and traditional development paradigms, then system stability is maintained, but adaptability and speed of change are reduced

Engineering Contradiction:
Improvespeed of changeVSAvoidcodebase complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments business processes into discrete, modular nodes that can be independently configured and connected. Each node represents a specific process step with its own parameters, allowing individual modifications without affecting the entire system. This modular segmentation enables rapid adaptation while managing complexity through organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system transitions from static hardcoded configurations to dynamic, runtime-configurable parameters. Configuration values are no longer fixed at compile time but can be adjusted during execution through the visual editor and parameter interface, allowing the system to adapt to changing business requirements without code changes.

Inventive Principle:
Principle #15Dynamics

2Speed

If existing systems operate as batch-based processes, then system simplicity is maintained, but responsiveness to real-time data is reduced

Engineering Contradiction:
Improvereal-time processing speedVSAvoidprocessing architecture complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system implements continuous event-driven processing where data flows through nodes in real-time rather than in batch cycles. Events trigger immediate processing actions as they occur, maintaining continuous useful action on incoming data streams. This enables real-time responsiveness while the event-driven architecture manages complexity through clear cause-effect relationships.

Inventive Principle:
Principle #20Continuity of useful action

3Ease of operation

If existing software systems are developed with traditional coding approaches, then development flexibility is maintained, but ease of interaction for non-coders is reduced

Engineering Contradiction:
Improveease of interactionVSAvoidautomation capability
Core Design Contradiction:
Ease of operationVSExtent of automation

Solution Approach 1:

The visual editor serves as an intermediary layer between users and the underlying complex system architecture. Instead of requiring direct programming knowledge, users interact with a graphical interface that translates their visual configurations into executable process flows. This mediator enables ease of operation while preserving full automation capability through the generated code.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system provides templates and reusable node patterns that can be copied and customized. Users can start with pre-defined process templates and modify them as needed, rather than creating processes from scratch. This copying mechanism simplifies the learning curve and enhances ease of operation while maintaining automation through the copied structural frameworks.

Inventive Principle:
Principle #26Copying

4Adaptability or versatility

If existing systems lack multi-system connectivity, then system simplicity is maintained, but versatility and integration capability are reduced

Engineering Contradiction:
Improvemulti-system connectivityVSAvoidintegration architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system employs universal connection interfaces and standardized data formats that enable nodes to communicate across different systems and platforms. Each node can be configured to interface with various external systems through unified connection mechanisms, providing multi-system connectivity without requiring separate integration architectures for each system type.

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

Data Source

PatentUS20220100554A1System and method for modifying a data processing method
Publication Date: 2022.03.31 COREZOID INC
  • US20220100554A1 patent drawing
  • US20220100554A1 patent drawing
  • US20220100554A1 patent drawing

AI summary

Disclosed herein are systems and methods for multi-system connectivity and automation via universal computing elements. Universal computing elements may comprise an object queue, one or more counters, and a function operating on parameters of objects in the object queue. Universal computing elements may be interconnected into processes of arbitrary complexity. Universal computing elements may facilitate modular and scalable business process development, including application programming interface and database connectivity. The processes may be stored in a repository accessible to multiple entities, and may be modified prior to being integrated into a process flow of at least one of the entities.