Hosted Client Instance Dependency Tables for ES Portfolio Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprise service (ES) owners face challenges in obtaining insights into the health and performance of their ES portfolios, as well as identifying potential impacts from other ES portfolios or local applications, due to the complexity of managing multiple ES configurations and dependencies across different applications.

Innovation Solution

A hosted client instance is provided with multiple application components that monitor events across applications using dependency tables, allowing for the display of relevant information in a user interface, enabling ES owners to manage and track the health and performance of their ES portfolios and potential impacts from other applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If multiple ES configurations and dependencies across different applications are managed, then comprehensive monitoring and insight into ES portfolio health is improved, but system complexity and difficulty of detection increase

Engineering Contradiction:
ImproveES portfolio health informationVSAvoidevent impact detection
Core Design Contradiction:
Loss of informationVSDifficulty of detecting and measuring

Solution Approach 1:

The system segments ES portfolios into distinct components with dedicated monitoring for each ES configuration. Dependency tables are organized by ES configuration, allowing targeted monitoring of specific ES components and their relationships. This segmentation enables comprehensive monitoring while reducing the complexity of tracking all dependencies simultaneously by breaking them down into manageable units.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Dependency tables serve as intermediaries between ES configurations and event monitoring. These tables mediate the relationship by pre-establishing dependency mappings that enable automatic impact analysis. When an event occurs, the intermediary dependency tables facilitate quick determination of affected ES configurations without requiring complex real-time analysis of all system relationships.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If dependency monitoring across applications is implemented, then proactive management capability is improved, but device complexity increases

Engineering Contradiction:
ImproveES portfolio reliabilityVSAvoidmonitoring system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Dependency tables are pre-configured with ES configuration relationships before operations begin. This preliminary setup enables proactive monitoring by having dependency mappings ready in advance. When events occur, the system can immediately reference pre-established dependency tables to determine impacts, eliminating the need for complex real-time dependency analysis and reducing operational complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The dependency tables serve multiple functions: they define ES configuration relationships, enable impact analysis, and support monitoring across different applications. By making dependency information multi-functional, the system reduces overall complexity compared to having separate mechanisms for each function, while still achieving comprehensive reliability monitoring.

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

Data Source

PatentUS11726796B2Platform-based enterprise technology service portfolio management
Publication Date: 2023.08.15 SERVICENOW INC
  • US11726796B2 patent drawing
  • US11726796B2 patent drawing
  • US11726796B2 patent drawing

AI summary

Techniques related to hosted client management comprising providing a hosted client instance over a network interface for communicatively coupling with a remote client device, the hosted client instance including a first application component for performing a first plurality of actions associated with the hosted client instance and a second application component for performing a second plurality of actions, monitoring, by the first application component, the second application component for an event associated with the second application component, determining that the event impacts the first application component based on one or more dependency tables associated with the second application component, and displaying, in a user interface of the first application component, information related to the event.