Event Manager for Automated Software Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual deployment of software in diverse environments and programming languages requires extensive expertise and time, with no real-time monitoring capabilities, leading to inefficient troubleshooting and restarts from the beginning upon failures.

Innovation Solution

An automated software deployment system using an event manager that identifies and processes instructions specific to the client, environment, and release packet, monitoring each step in real-time and allowing for resumed deployment at failed points without user intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual deployment is performed by software developers and engineers, then deployment can be completed with human oversight, but extensive expertise and time are required, and troubleshooting is inefficient

Engineering Contradiction:
Improvedeployment reliabilityVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The deployment system performs self-service through automated workflow execution. The system automatically loads release packets, executes deployment workflows, monitors progress, and handles troubleshooting without requiring continuous human intervention. This eliminates the time-consuming manual operations while maintaining deployment reliability through automated oversight mechanisms.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Manual mechanical deployment operations are replaced by an automated computer-based system. The system substitutes human developers and engineers with automated processes that can execute workflows, monitor deployment status, and perform troubleshooting operations electronically, significantly reducing deployment time while maintaining reliability.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Adaptability or versatility

If manual deployment processes are used, then flexibility in handling diverse environments and programming languages is possible, but the complexity of managing multiple tools and languages increases

Engineering Contradiction:
Improveenvironment adaptabilityVSAvoiddeployment system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The deployment system achieves universality by designing a single automated workflow engine that can handle multiple deployment environments and programming languages through standardized interfaces. The system loads release packets containing environment-specific configurations and executes appropriate workflows automatically, eliminating the need for separate manual processes for each environment while reducing overall system complexity.

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

Solution Approach 2:

The system introduces an intermediary automated deployment engine that mediates between diverse deployment environments and the user. This intermediary layer handles the complexity of different environments and programming languages internally, presenting a simplified interface to users while maintaining adaptability to various deployment scenarios through standardized workflow mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If workflow execution is performed without real-time monitoring, then the deployment process can run autonomously, but troubleshooting becomes difficult and requires restarting from the beginning

Engineering Contradiction:
Improvedeployment efficiencyVSAvoiddeployment status monitoring
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The deployment system implements feedback mechanisms by continuously monitoring workflow execution status and providing real-time information about deployment progress. The system tracks each step of the workflow, detects failures automatically, and provides feedback signals that enable targeted troubleshooting without requiring restarts, thereby maintaining high deployment efficiency while improving detectability of deployment status.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10585656B1Event manager for software deployment
Publication Date: 2020.03.10 CERNER INNOVATION INC
  • US10585656B1 patent drawing
  • US10585656B1 patent drawing
  • US10585656B1 patent drawing

AI summary

Methods, systems, and computer-readable media are disclosed herein that facilitate automatically audited software deployment. When a software deployment event is scheduled by a user, an event manager selects and bundles data, properties, and computer readable instructions for the deployment based on a particular client, environment, and/or release packet. At the scheduled time, the event manager automatically triggers deployment of the software via an integration manager, without the need for a software engineer. The event manager monitors the integration manager throughout processing of workflow to deploy software of the release packet. In near real-time, the event manager identifies when a failure occurs, identifies the specific cause of failures in a workflow, and sends the information as an alert to a user. The event manager also facilitates restarting processing of a workflow at a particular failed step.