Methods for identifying or predicting capacity problems

• US 20040083116A1
• Filed: 01/16/2003
• Published: 04/29/2004
• Est. Priority Date: 10/25/2002
• Status: Abandoned Application

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Inventors: Joyce, Derek J.
• Application Number:
  US10/345,850
• Publication Number:
  US 20040083116A1
• Time in Patent Office: Days
• US Class Current: 705/1
• CPC Class Codes: G06F 11/008 Reliability or availability analysis
• CPC Class Codes: G06Q 10/06312 Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
• CPC Class Codes: G06Q 10/06393 Score-carding, benchmarking or key performance indicator [KPI] analysis
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Methods to identify and predict capacity problems in systems. The methods of the invention involve identifying, defining, and separating: (1) the set of internal capacity parameters, (2) the set of external capacity parameters, and (3) key performance indicators, for system administrator analysis. Such separation of these sets of variables and parameters followed by their presentation in a data-management framework, greatly enhances the capability of a system administrator to detect and predict capacity problems.

Claims

1. A method for identifying or predicting capacity problems in a system comprising:

(a) identifying at least one internal capacity variable for the system;

(b) identifying at least one external capacity variable for the system;

(c) identifying at least one key performance indicator for the system;

(d) constructing a data-management framework comprising and separately setting forth;

(i) the internal capacity variable, and

(ii) the external capacity variable;

(e) defining at least one target key performance indicator;

(f) defining at least one external-capacity-variable range for the external capacity variable;

(g) defining at least one future growth parameter for the external capacity variable; and

(h) analyzing the future growth parameter and the external-capacity-variable range in view of the data-management framework to identify the capacity problem.

2. The method of claim 1, wherein the key performance indicator relates to a parameter, or a rate.

3. The method of claim 2, wherein the parameter or the rate comprises a time taken by the system to complete a process or a portion thereof;

a volume the system is handling;

a cost to run the system or process;

errors or defects per unit time;

or transactions or cycles per unit time.

4. The method of claim 1, wherein the data-management framework is stored in a computer-readable medium.

5. The method of claim 1, wherein the data-management framework is stored in random access memory.

6. The method of claim 1, wherein the system comprises computer resources, for use by one or more users, comprising random access memory and one or more computer processors programmed with one or more computer software applications.

7. The method of claim 6, wherein the internal capacity variable relates to:

(a) a number of the software applications,

(b) a complexity of one or more of the software applications,

(c) a speed at which data can be accessed or downloaded

(d) a speed at which data can be processed by one or more of the computer software applications, or

(e) an amount of the computer resources available.

8. The method of claim 6, wherein the external capacity variable relates to:

(a) a time deadline;

(b) complexity of an analysis;

(c) an amount or nature of data;

(d) a number of users;

or

(e) a time one or more users will wait.

9. The method of claim 6, wherein the key performance indicator relates to usage of available computer resources.

10. The method of claim 6, wherein one or more of the software applications is designed to capture trades;

execute trades;

price financial instruments;

manage risk;

calculate position;

calculate profit or loss;

process financial-instrument transaction settlements, process financial-instrument transaction confirmations, process and reconciliate financial accounts, or provide internal and client reporting.

11. The method of claim 6, wherein the computer resources are subject to the control of a system administrator and wherein the internal capacity variable is within the control of a system administrator.

12. The method of claim 11, wherein the internal capacity variable relates to:

(a) a number of the software applications,

(b) complexity of one or more of the software applications,

(c) a speed at which data can be accessed or downloaded

(d) a speed at which data can be processed by one or more of the computer software applications, or

(e) an amount of the computer resources available.

13. The method of claim 6, wherein the external capacity variable is outside the control of the system administrator.

14. The method of claim 13, wherein the external capacity variable relates to:

(a) a time deadline;

(b) complexity of an analysis;

(c) an amount or nature of data;

(d) a number of users;

or

(e) a time one or more users will wait.

15. The method of claim 6, wherein one or more of the computer software applications is designed to process financial data.

16. The method of claim 15, wherein the financial data relates to one or more financial instruments.

17. The method of claim 16, wherein one or more of the financial instruments is an equity, equity derivative, bond, interest-rate derivative, currency, currency derivative, commodities contract, future, option, swap, or credit derivative.