# US 2006/0153090 A1 · Method for supporting on-demand performance

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2006/0153090 A1
- Document ID: US20060153090A1
- Status: Published application
- Kind: A1
- Application number: 11/034,905
- Filed: 2005-01-13
- Published: 2006-07-13
- Earliest claimed: 2005-01-13
- Assignees: International Business Machines Corporation
- Inventors: Ellis Bishop; Randy Johnson; James Kenley; Tedrick Northway; H. Rinckel; Clea Zolotow
- Web page: https://patentgrep.com/patent/US20060153090A1

## CPC

- H04L 67/61: taking into account QoS or priority requirements
- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- G06F 11/3447: {Performance evaluation by modeling}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method is disclosed for managing the performance of shared computing resources in furtherance of delivering on-demand IT services to multiple customers. The inventive method comprises predicting the performance of resources allocated among the customers to minimize performance related problems; preventing performance related problems by evaluating the impact of changes in resource allocations; reacting to performance alerts to resolve performance related problems; and determining the appropriate level of resource performance needed in service level agreements, and that these requirements detailed in the service level agreements are achieved. This Performance Management method ensures that the demands of the customers are not affected by the allocation and utilization of the shared IT resources.

## Claims

### Claim 1

A method for predicting, avoiding, and minimizing performance problems in a shared computing system, at the system and subsystem level, the method comprising the steps of:
monitoring performance data;
analyzing performance data to identify a performance trend;
identifying approaching performance degradation in the performance trend;
identifying a component that the approaching performance degradation impacts;
identifying a performance parameter that impacts the component;
determining if a system limitation constrains the performance parameter;
responsive to determining that a system limitation does not constrain the performance parameter,
comparing the performance trend with a hypothetical optimum performance trend to identify a parameter adjustment that returns the impacted component to acceptable performance,
recommending the parameter adjustment to a primary support group and an account team,
gaining approval of the recommendation from the primary support group and the account team,
and implementing the recommendation to resolve the approaching performance degradation; and
responsive to determining that a system limitation does constrain the performance parameter,
communicating the system limitation to an appropriate party, and
opening a change request to resolve the system limitation.

### Claim 2 (depends on 1)

The method of claim 1 wherein the performance data comprises:
a key indicator report;
historical real-time data; and
a service level agreement metric.

### Claim 3 (depends on 2)

The method of claim 2 wherein the key indicator report is a system key indicator report.

### Claim 4 (depends on 2)

The method of claim 2 wherein the key indicator report is a subsystem key indicator report.

### Claim 5 (depends on 1)

The method of claim 1 wherein identifying approaching performance degradation comprises the steps of:
identifying an exception in the performance trend; and
identifying an anomaly and at least one specific metric in the performance data where the exception exists.

### Claim 6 (depends on 1)

The method of claim 1 wherein implementing the recommendation to resolve the approaching performance degradation comprises the steps of:
determining if the performance degradation causes an immediate delivery impact;
responsive to determining that the performance degradation does not cause an immediate delivery impact, opening a change request to implement the parameter adjustment and managing the change request;
responsive to determining that the approaching performance degradation causes an immediate delivery impact, invoking the manage problems process to manage the problem record to resolve the performance issue.

### Claim 7

A method for reacting to a change request to avoid negative performance effects in a shared computing system, the process comprising the steps of:
determining if the change request impacts the shared computing system;
responsive to determining that the change request impacts the shared computing system, obtaining change approval status, and minimizing the impact of the change request; and
responsive to determining that the change request does not impact the shared computing system,
approving the change request, and
updating and documenting any change report that includes the change request.

### Claim 8 (depends on 7)

The method of claim 7 wherein minimizing the impact of the change request comprises the step of:
modifying the change request.

### Claim 9 (depends on 7)

The method of claim 7 wherein minimizing the impact of the change request comprises the step of:
rejecting the change request.

### Claim 10 (depends on 7)

The method of claim 7 wherein minimizing the impact of the change request comprises the step of:
postponing the change request.

### Claim 11 (depends on 7)

The method of claim 7 further comprising the steps of:
determining if additional data is required to evaluate the change request; and
responsive to determining that an additional report is required to evaluate the change request, generating an ad hoc report containing the additional data.

### Claim 12

A method for reacting to an alert in a shared computing system, the process comprising the steps of:
determining if the alert is a performance alert;
responsive to determining the alert is not a performance alert,
identifying a service group that should receive the alert, and
routing the alert to the service group;
responsive to determining that the alert is a performance alert, determining if the performance alert is valid;
responsive to determining the performance alert is invalid, documenting an alert change that corrects the invalid performance alert; and
responsive to determining the performance alert is valid,
determining if additional data is required to evaluate the performance alert,
responsive to determining that additional data is required to evaluate the performance alert, generating an ad hoc report containing the additional data,
identifying a component of the shared computing system that caused the performance alert,
identifying a variable in the component that caused the performance alert,
modifying the variable to resolve the performance alert,
monitoring the component to ensure the performance alert is resolved, and
documenting the modification to the variable.

### Claim 13

A process for managing the performance of resources in a shared computing system to meet requirements of a contract governing a service level agreement, the process comprising the steps of:
reviewing the contract, the service level agreement, and a technology strategy;
identifying a performance parameter to be monitored for ensuring that the service level agreement is satisfied;
establishing a performance baseline for the performance parameter;
defining a performance threshold, based on the performance parameter and the performance baseline, for alerting a Performance Analyst when a performance parameter crosses the performance threshold;
gaining approval for the performance threshold from an account team to ensure the service level agreement satisfies the requirements of the contract;
defining a performance alert and a response to the performance alert;
incorporating the defined performance alert, the performance threshold, and the response into the service level agreement; and
monitoring the system performance to ensure the requirements of the service level agreement are satisfied.

### Claim 14 (depends on 13)

The method of claim 13 wherein monitoring the system performance to ensure the requirements of the service level agreement are satisfied comprises the steps of:
establishing data collection requirements;
requesting a measurement team collect data and report data according to the data collection requirements;
receiving and reviewing a report of the data collected by the measurement team; and
changing the performance alert and the performance threshold to meet the requirements of the service level agreement.

### Claim 15 (depends on 14)

The method of claim 14 wherein the step of changing the performance alert and the performance threshold to meet the requirements of the service level agreement comprises:
changing the performance alert and the performance threshold at the system level to meet the requirements of the service level agreement.

### Claim 16 (depends on 14)

The method of claim 14 wherein the step of changing the performance alert and the performance threshold to meet the requirements of the service level agreement comprises:
changing the performance alert and the performance threshold at the subsystem level to meet the requirements of the service level agreement.

### Claim 17

A method for managing the performance of a shared computing system, the method comprising:
a step for evaluating and monitoring performance data and predicting performance problems;
a step for reviewing a planned event and preventing performance problems;
a step for reacting to a performance alert; and
a step for establishing performance measurements, thresholds, and alerts so that the requirements of a service level agreement are satisfied.

### Claim 18 (depends on 17)

The method of claim 17 wherein the performance data is system performance data.

### Claim 19 (depends on 17)

The method of claim 17 wherein the performance data is subsystem performance data.

### Claim 20 (depends on 17)

The process of claim 17 wherein the step for evaluating and monitoring performance data and predicting performance problems comprises:
monitoring performance data;
analyzing performance data to identify a performance trend;
identifying approaching performance degradation in the performance trend;
identifying a component that the approaching performance degradation impacts;
identifying a performance parameter that impacts the component;
determining if a system limitation constrains the performance parameter;
responsive to determining that a system limitation does not constrain the performance parameter,
comparing the performance trend with a hypothetical optimum performance trend to identify a parameter adjustment that returns the impacted component to acceptable performance,
recommending the parameter adjustment to a primary support group and an account team,
gaining approval of the recommendation from the primary support group and the account team,
and implementing the recommendation to resolve the approaching performance degradation; and
responsive to determining that a system limitation does constrain the performance parameter,
communicating the system limitation to an appropriate party, and
opening a change request to resolve the system limitation.

### Claim 21 (depends on 20)

The method of claim 20 wherein the performance data is system performance data.

### Claim 22 (depends on 20)

The method of claim 20 wherein the performance data is subsystem performance data.

### Claim 23 (depends on 17)

The method of claim 17 wherein the planned event is a change request, and the step for reviewing the planned event and preventing performance problems comprises:
determining if the change request impacts the shared computing system;
responsive to determining that the change request impacts the shared computing system,
obtaining change approval status, and
minimizing the impact of the change request; and
responsive to determining that the change request does not impact the shared computing system,
approving the change request, and
updating and documenting any change report that includes the change request.

### Claim 24 (depends on 17)

The method of claim 17 wherein the step for reacting to an alert comprises:
determining if the alert is a performance alert;
responsive to determining the alert is not a performance alert,
identifying a service group that should receive the alert, and
routing the alert to the service group;
responsive to determining that the alert is a performance alert, determining if the performance alert is valid;
responsive to determining the performance alert is invalid, documenting an alert change that corrects the invalid performance alert; and
responsive to determining the performance alert is valid,
determining if additional data is required to evaluate the performance alert,
responsive to determining that additional data is required to evaluate the performance alert, generating an ad hoc report containing the additional data,
identifying a component of the shared computing system that caused the performance alert,
identifying a variable in the component that caused the performance alert,
modifying the variable to resolve the performance alert,
monitoring the component to ensure the performance alert is resolved, and
documenting the modification to the variable.

### Claim 25 (depends on 24)

The method of claim 24 wherein the alert is a system alert.

### Claim 26 (depends on 24)

The method of claim 24 wherein the alert is a subsystem alert.

### Claim 27 (depends on 17)

The method of claim 17 wherein the service level agreement is governed by a contract, and the step for establishing performance measurements, thresholds, and alerts comprises:
reviewing the contract, the service level agreement, and a technology strategy;
identifying a performance parameter to be monitored for ensuring that the service level agreement is satisfied;
establishing a performance baseline for the performance parameter;
defining a performance threshold, based on the performance parameter and the performance baseline, for alerting a Performance Analyst when a performance parameter crosses the performance threshold;
gaining approval for the performance threshold from an account team to ensure the service level agreement satisfies the requirements of the contract;
defining a performance alert and a response to the performance alert;
incorporating the defined performance alert, the performance threshold, and the response into the service level agreement; and
monitoring the system performance to ensure the requirements of the service level agreement are satisfied.

### Claim 28 (depends on 27)

The method of claim 27 wherein the performance parameter is a system performance parameter.

### Claim 29 (depends on 27)

The method of claim 27 wherein the performance parameter is a subsystem performance parameter.

### Claim 30 (depends on 17)

The method of claim 17 wherein the step for evaluating and monitoring performance data and predicting performance problems comprises:
monitoring performance data;
analyzing performance data to identify a performance trend;
identifying approaching performance degradation in the performance trend;
identifying a component that the approaching performance degradation impacts;
identifying a performance parameter that impacts the component;
determining if a system limitation constrains the performance parameter;
responsive to determining that a system limitation does not constrain the performance parameter,
comparing the performance trend with a hypothetical optimum performance trend to identify a parameter adjustment that returns the impacted component to acceptable performance,
recommending the parameter adjustment to a primary support group and an account team,
gaining approval of the recommendation from the primary support group and the account team,
and implementing the recommendation to resolve the approaching performance degradation; and
responsive to determining that a system limitation does constrain the performance parameter,
communicating the system limitation to an appropriate party, and
opening a change request to resolve the system limitation;
and wherein the planned event is a change request, and the step for reviewing the planned event and preventing performance problems comprises:
determining if the change request impacts the shared computing system;
responsive to determining that the change request impacts the shared computing system,
obtaining change approval status, and
minimizing the impact of the change request; and
responsive to determining that the change request does not impact the shared computing system,
approving the change request, and
updating and documenting any change report that includes the change request;
and wherein the step for reacting to a performance alert comprises:
determining if the alert is a performance alert;
responsive to determining the alert is not a performance alert,
identifying a service group that should receive the alert, and
routing the alert to the service group;
responsive to determining that the alert is a performance alert, determining if the performance alert is valid;
responsive to determining the performance alert is invalid, documenting an alert change that corrects the invalid performance alert; and
responsive to determining the performance alert is valid,
determining if additional data is required to evaluate the performance alert,
responsive to determining that additional data is required to evaluate the performance alert, generating an ad hoc report containing the additional data,
identifying a component of the shared computing system that caused the performance alert,
identifying a variable in the component that caused the performance alert,
modifying the variable to resolve the performance alert,
monitoring the component to ensure the performance alert is resolved, and
documenting the modification to the variable;
and wherein the service level agreement is governed by a contract, and the step for establishing performance measurements, thresholds, and alerts comprises:
reviewing the contract, the service level agreement, and a technology strategy;
identifying a performance parameter to be monitored for ensuring that the service level agreement is satisfied;
establishing a performance baseline for the performance parameter;
defining a performance threshold, based on the performance parameter and the performance baseline, for alerting a Performance Analyst when a performance parameter crosses the performance threshold;
gaining approval for the performance threshold from an account team to ensure the service level agreement satisfy the requirements of the contract;
defining a performance alert and a response to the performance alert;
incorporating the defined performance alert, the performance threshold, and the response into the service level agreement; and
monitoring the system performance to ensure the requirements of the service level agreement are satisfied.

### Claim 31 (depends on 30)

The method of claim 30 wherein the performance data is system performance data.

### Claim 32 (depends on 30)

The method of claim 30 wherein the performance data is subsystem performance data.
