Runbook Automation via Operator Activity Capture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional runbook automation processes are time-consuming and expensive due to the need for additional effort to convert human-readable runbooks into automated formats, and they often require programming expertise, with runbooks being incomplete and needing constant upkeep due to system complexity and rapid change.

Innovation Solution

A computer system that automatically generates and updates runbook workflows based on operator activity to remediate error causes, using a Root-Cause Analysis module to identify issues and a Runbook Automation module to create and store generic or updated runbooks for similar errors, enabling rapid retrieval and application of corrective actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If conventional runbook automation processes are used to convert human-readable runbooks into automated formats, then automation capability is achieved, but the process becomes time-consuming and expensive

Engineering Contradiction:
Improverunbook automation capabilityVSAvoidconversion time
Core Design Contradiction:
Extent of automationVSLoss of time

Solution Approach 1:

The system automatically generates executable workflows by monitoring and analyzing operator interactions with the IT system. The runbook automation module captures operator actions and automatically converts them into automated workflows without requiring manual programming or conversion effort, making the system self-updating and self-maintaining

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the manual mechanical process of converting runbooks with an automated digital system. Instead of manually translating human-readable runbooks into automated formats, the system uses software to automatically generate executable workflows from observed operator behavior, eliminating the need for manual conversion work

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

2Extent of automation

If conventional runbook automation processes are used to convert human-readable runbooks into automated formats, then automation capability is achieved, but programming expertise is required

Engineering Contradiction:
Improverunbook automation capabilityVSAvoidease of creation
Core Design Contradiction:
Extent of automationVSEase of manufacture

Solution Approach 1:

The system performs automatic generation of executable workflows through the runbook automation module, which captures operator actions and translates them into automated workflows without requiring human programming expertise. The system serves itself by automatically updating its own automation logic based on observed operations

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The runbook automation module acts as an intermediary between operator actions and the automated workflow system. It captures the natural interactions of operators with the IT system and automatically translates these into executable workflows, serving as a mediator that eliminates the need for programmers to manually create automation logic

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If runbooks are created manually to cover all anticipated scenarios, then completeness is improved, but the runbooks need constant upkeep due to system complexity and rapid change

Engineering Contradiction:
Improverunbook completenessVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system transitions from static, manually-maintained runbooks to dynamic, automatically-updating workflows. The runbook automation module continuously monitors operator interactions and automatically updates the executable workflows to reflect current system behavior, ensuring the automation remains synchronized with the evolving IT system without manual intervention

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements a feedback loop where the runbook automation module continuously monitors operator actions and system state, then uses this feedback to automatically update and refine the executable workflows. This closed-loop approach ensures the automation adapts to system changes and maintains completeness without requiring manual review and updates

Inventive Principle:
Principle #23Feedback

4Productivity

If detailed expert knowledge is encoded in runbooks for rapid response, then response quality is improved, but the creation and maintenance becomes more complex

Engineering Contradiction:
Improveresponse speedVSAvoidrunbook complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system automatically captures and encodes expert knowledge through the runbook automation module, which monitors and records the actions of experienced operators. This self-updating capability allows the system to accumulate expert knowledge over time without increasing manual complexity, as the automation module handles the encoding and organization of procedures automatically

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent merges the knowledge capture process with the automation creation process. The runbook automation module simultaneously observes operator actions, extracts procedural knowledge, and generates executable workflows in a single integrated process, eliminating the separate steps of documentation and automation creation that would otherwise increase complexity

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9891971B1Automating the production of runbook workflows
Publication Date: 2018.02.13 EMC IP HLDG CO LLC
  • US9891971B1 patent drawing
  • US9891971B1 patent drawing
  • US9891971B1 patent drawing

AI summary

A method and program product for receiving an indication of a particular root cause associated with an error condition in an information technology (IT) system, electronically capturing activity of an operator for the IT system, automatically generating a workflow portion for a generic runbook, and storing the generic runbook in a manner that allows retrieval of the generic runbook.