Collaborative Runbook Execution With Dynamic Operation Delegation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing runbook execution systems lack efficient collaboration mechanisms for delegating operations between users with varying authority levels, technical expertise, and access rights, leading to inefficiencies in diagnosing and remediating IT system events.

Innovation Solution

A collaborative runbook execution system that allows users to delegate operations to other users or groups based on authority levels, technical expertise, and access rights, using a runbook execution platform with a collaboration engine that facilitates ownership transfer and metadata management for seamless collaboration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If users execute runbook operations independently without collaboration mechanisms, then each user can operate autonomously, but efficiency decreases when users need to delegate operations to others with different authority levels

Engineering Contradiction:
Improverunbook execution efficiencyVSAvoidcollaboration mechanism complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces a collaboration engine as an intermediary component that mediates between users with different authority levels. This engine handles ownership transfer, delegates operations appropriately, and manages metadata automatically, enabling efficient collaboration without requiring complex manual coordination between users.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The collaboration mechanism operates autonomously by automatically detecting authority levels, transferring ownership between users, and managing metadata without requiring manual intervention. The system self-manages the collaboration process, reducing the operational burden on users while maintaining efficiency.

Inventive Principle:
Principle #25Self-service

2Reliability

If the system tracks detailed metadata for each user operation, then collaboration and authorization are precise, but system complexity increases

Engineering Contradiction:
Improveauthorization accuracyVSAvoidmetadata management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The metadata structure serves multiple functions simultaneously: it tracks user identity, authorization levels, ownership information, and operation history. By designing a universal metadata framework, the system achieves precise authorization tracking without requiring separate complex systems for each function.

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

Solution Approach 2:

The system continuously updates metadata based on user actions and authority level changes, providing feedback loops that automatically adjust permissions and ownership. This dynamic metadata management maintains authorization accuracy while reducing manual complexity through automated updates.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4392865B1Collaborative runbook execution
Publication Date: 2025.07.02 ORACLE INT CORP
  • EP4392865B1 patent drawingFigure 1
  • EP4392865B1 patent drawingFigure 2
  • EP4392865B1 patent drawingFigure 3

AI summary

Techniques for collaboratively executing runbook sessions are disclosed. A system provides for collaborative completion of runbook operations by delegating runbook operations or by transferring ownership of a runbook from one user to another. A system identifies a first set of runbook operations capable of being completed by a first user. The system identifies a second set of runbook operations that are not capable of being completed by the first user. The system identifies a second user capable of completing the second set of runbook operations. Upon completion of the first set of runbook operations by the first user, the system determines whether to delegate the second set of runbook operations to the second user or to transfer ownership of the runbook session to the second user. The system determines that the runbook session is completed based on the combined results collaboratively generated by the initial user and the alternate user.