Job Chain Data Structure for Automated Task Execution

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing enterprise software systems face challenges in efficiently managing and executing complex processes comprising multiple steps or tasks, as they often require manual configuration and lack a streamlined mechanism for creating and executing job chains with consistent metadata propagation and user-friendly UI visualization.

Innovation Solution

The introduction of a job chain data structure with associated metadata allows for the creation and execution of multiple tasks as a single entity, enabling users to define and schedule job chains by referencing existing simple jobs, with automatic propagation of parameters and attributes, and flexible UI rendering options, facilitating consistent reporting and user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration is used for each task in a complex process, then flexibility and control are improved, but time consumption and operational complexity increase

Engineering Contradiction:

Improvemanual configuration flexibilityVSAvoidtime consumption for configuration

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

Multiple simple jobs are merged into a single job chain entity that can be executed as one unit. The job chain data structure combines multiple task definitions, parameters, and execution logic into a unified object that represents the entire complex process, eliminating the need to configure and manage each task separately.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary actions by automatically generating job chain instances from templates and pre-configuring metadata structures before execution. Job chain templates pre-define the sequence of tasks, parameters, and relationships, so when a job chain is created, the configuration work has already been done in advance, reducing manual effort at execution time.

Inventive Principle:

Principle #10Preliminary action

2Manufacturing precision

If complex processes are broken down into multiple simple tasks, then execution precision and control are improved, but system complexity and coordination overhead increase

Engineering Contradiction:

Improveexecution precision of individual tasksVSAvoidsystem complexity for managing multiple tasks

Core Design Contradiction:

Manufacturing precisionVSDevice complexity

Solution Approach 1:

The complex process is segmented into discrete simple jobs that can be independently defined, executed, and monitored. Each simple job represents a distinct task with specific parameters and execution logic, allowing for precise control while maintaining modularity. The job chain data structure manages these segments through standardized references and metadata.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The job chain data structure serves multiple functions simultaneously: it defines the sequence of tasks, stores execution parameters, manages metadata propagation, handles error recovery logic, and coordinates resource allocation. This universal structure reduces system complexity by consolidating what would otherwise require multiple separate coordination mechanisms.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Stability of the object's composition

If metadata is propagated manually across multiple tasks, then data consistency is improved, but labor intensity and error probability increase

Engineering Contradiction:

Improvemetadata consistencyVSAvoideffort required for metadata propagation

Core Design Contradiction:

Stability of the object's compositionVSEase of manufacture

Solution Approach 1:

The system performs self-service by automatically propagating metadata from parent job chain definitions to child job instances through the data structure. When a job chain is created or modified, the system automatically updates all referenced tasks and parameters, ensuring consistency without manual intervention. The metadata propagation is handled by the job chain execution logic itself.

Inventive Principle:

Principle #25Self-service

4Productivity

If job chains are created from templates, then creation speed and consistency are improved, but adaptability to specific cases may be reduced

Engineering Contradiction:

Improvejob chain creation speedVSAvoidflexibility for specific configurations

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The job chain data structure is designed to be dynamic, allowing templates to define default configurations while permitting runtime modifications. Parameters can be overridden during job chain instance creation, and the execution engine adapts the standardized structure to specific case requirements through parameter substitution and conditional logic within the job chain definition.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS10203984B2Data structure for multiple executable tasks

Publication Date: 2019.02.12 SAP SE

AI summary

A system, method, and computer-readable medium, including receiving a request to create a job chain, the job chain being a data structure and to reference a plurality of simple jobs; specifying the plurality of simple jobs referenced by the job chain, each of the simple jobs including at least one attribute defining an executable task for the simple job; specifying an order of execution for the plurality of simple jobs referenced by the job chain; and generating an instance of the job chain data structure, the generated job chain referencing the plurality of simple jobs and inheriting the at least one attribute of each of the plurality of simple jobs.