Lifecycle Orchestration System for Computing Processes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computing systems lack a centralized system for incorporating and managing various process flows from separate sources to orchestrate the lifecycle execution and monitoring of computing processes, leading to inefficiencies in addressing complex problems and issues.

Innovation Solution

A computer-implemented method and system that orchestrates the execution of computing processes by receiving input events, determining associated tasks, selecting process flows based on models, and executing executable actions to transition the system between defined states, utilizing federated data sources and microservices for generating output events and updating processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a centralized system for lifecycle orchestration is implemented, then process management capability is improved, but system complexity increases

Engineering Contradiction:
Improveprocess management capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments process flows into discrete executable actions that can be independently managed and executed. Each process flow is broken down into actionable units that can be orchestrated centrally while maintaining modular independence, reducing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A centralized lifecycle orchestration system acts as an intermediary between federated data sources and execution environments. This mediator coordinates process flows across multiple sources without requiring direct integration between them, managing complexity centrally while preserving source independence.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If multiple federated data sources are integrated, then data availability is improved, but integration complexity increases

Engineering Contradiction:
Improvedata availabilityVSAvoidintegration complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system implements a universal process flow execution framework that can handle multiple federated data sources through a common interface. This multi-functional approach allows the same orchestration mechanism to work with diverse data sources without requiring source-specific integration logic.

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

Solution Approach 2:

The centralized orchestration system serves as an intermediary layer between federated data sources and the execution engine. This mediator abstracts the complexity of integrating multiple data sources, presenting a unified interface while managing the underlying diversity of source systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If process flows are executed with multiple states and transitions, then process control precision is improved, but execution complexity increases

Engineering Contradiction:
Improveprocess control precisionVSAvoidexecution complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

Process flows are segmented into discrete states and executable actions, with clear transition definitions between them. This segmentation allows precise control of process progression while managing complexity through structured, atomic process units that can be independently validated and executed.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20240411585A1Lifecycle orchestration
Publication Date: 2024.12.12 CAPITAL ONE SERVICES LLC
  • US20240411585A1 patent drawing
  • US20240411585A1 patent drawing
  • US20240411585A1 patent drawing

AI summary

A method, a system, and a computer program product for lifecycle orchestration. An input computing event generated by a computing application executing in a computing system is received. A plurality of tasks associated with the input computing event is determined. A process flow is selected from a plurality of process flows based on one or more models defining one or more states of the computing system during execution of each process flow and a plurality of executable actions for performing tasks. At least one executable action for performing at least one task is executed resulting in the computing system being transferred from one state to another. An output computing event resulting from the executing of the executable action is generated. While the computing system is in another state, another executable action for performing another task is executed, where the generated output computing event is input to the executing of another executable action.