Autonomic SLA Breach Value Estimation System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manually selecting SLA breach values is complex and time-consuming, as it requires specifying thresholds for resource performance measurements and time periods, making it difficult to establish effective service level agreements in a policy-based service differentiation model.

Innovation Solution

An SLA breach value estimator system that includes a communicative coupling to performance history data and a graphical user interface for proposing and configuring SLA breach values, using methods such as aggregated, specific customer, customer resource subset, and predictive processes to estimate acceptable breach values, ensuring probable compliance with specified thresholds.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If SLA breach values are manually selected during configuration, then the service level agreement can be established with customized thresholds, but the process becomes complex and time-consuming

Engineering Contradiction:
ImproveSLA breach value accuracyVSAvoidconfiguration time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary analysis of historical performance data to pre-calculate recommended breach values before the user needs to configure the SLA. By analyzing past performance patterns in advance, the system prepares suggested thresholds that can be directly applied, eliminating the need for manual analysis and configuration time while maintaining accurate, data-driven breach values.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If multiple estimation processes are provided (aggregated, specific customer, customer resource subset, predictive), then the system can accommodate different service differentiation needs, but the device complexity increases

Engineering Contradiction:
Improveservice differentiation capabilityVSAvoidestimator structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The estimation system is divided into distinct modular processes: aggregated process for general recommendations, specific customer process for customer-specific analysis, customer resource subset process for resource-specific tuning, and predictive process for future-oriented estimates. Each process handles a specific aspect of the estimation task independently, allowing the system to provide versatile service differentiation while keeping each individual process simple and manageable.

Inventive Principle:
Principle #1Segmentation

3Manufacturing precision

If SLA breach values are manually configured with multiple parameters (resource performance measurement, measurement time period, target set of resources), then precise control over SLA terms is achieved, but the ease of operation decreases

Engineering Contradiction:
ImproveSLA term specificationVSAvoidbreach value configuration
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The system automatically performs the complex task of analyzing historical performance data and generating recommended breach values without requiring manual input from the user. The estimator self-services by autonomously processing performance measurements, time periods, and resource targets, then presenting ready-to-use recommendations. This maintains precise SLA term specification while dramatically improving ease of operation, as users only need to review and approve pre-calculated values rather than manually configuring multiple parameters.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8775585B2Autonomic SLA breach value estimation
Publication Date: 2014.07.08 SERVICENOW INC
  • US8775585B2 patent drawing
  • US8775585B2 patent drawing
  • US8775585B2 patent drawing

AI summary

A method, system and apparatus for estimating an SLA breach value. The method can include processing resource data to identify an acceptable SLA breach value; and, displaying the acceptable SLA breach value through a user interface. The processing step can include identifying a best practices SLA breach value based upon resource data for an aggregation of customers. Alternatively, the processing step can include identifying an average SLA breach value for a specific customer. As a further alternative, the identifying step can include identifying an average SLA breach value for a specific customer for a specific resource. As yet a further alternative, the processing step can include identifying an SLA breach value trend based upon past measured historical systems management data; and, predicting a future SLA breach value based upon the trend. In all cases, the acceptable SLA breach value can be increased by a fixed proportion.