Method for proactive planning

• US 6,032,121 A
• Filed: 05/15/1997
• Issued: 02/29/2000
• Est. Priority Date: 05/15/1997
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Dietrich, Brenda Lynn, O'Leary, Thomas, Rushmeier, Russell Alan, Shannon, David Lawton, Wang, Robert
• Primary Examiner(s): MacDonald, Allen R.
• Assistant Examiner(s): Kanof, Pedro R.
• Application Number:
  US08/856,854
• Time in Patent Office: 1,020 Days
• Field of Search: 705/8, 705/3, 705/28, 705/26, 701/202, 701/23, 364/468.06, 364/468.01, 707/3, 345/163, 370/248
• US Class Current: 705/7.22
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/0631 Resource planning, allocation, distributing or scheduling for enterprises or organisations
• 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/06314 Calendaring for a resource
• CPC Class Codes: G06Q 10/0637 Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders

Abstract

A proactive planning methodology and system. The invention reconceptualizes current (delimited) calendar-based planning approaches, where planning is done at fixed or arbitrary times, in favor of a proactive planning methodology which can use information about real time changes in input data used for planning, for determining when a revised plan should be generated. The proactive planning methodology may determine, inter alia, that immediate planning is necessary, or it may schedule the generation of a new plan at some time in the future.

Claims

1. A computer-implemented method for proactive planning comprising:

1) employing a planning engine comprising processes for generating an executable plan for a known period of execution;

2) inputting to the planning engine real time planning data, said planning data being derived by an automated process from real enterprise data;

3) monitoring said input planning data;

4) utilizing said input ping data selectively for determining if and/or when the executable plan is to be revised during said period of execution by said planning engine, such that depending upon a magnitude of change, as represented by said input planning data, to said executable plan, said planning engine is selectively employed; and

5) allocating resources based on said determining.

2. A method according to claim 1, further comprising using information about changes in the input planning data for determining if the executable plan is to be revised during said period of execution.

3. A method according to claim 2, further comprising using information about changes in the input planning data for determining when a revised plan is to become executable.

4. A method according to claim 1, further comprising implementing a revised executable plan in response to any detected change in the input planning data.

5. A method according to claim 1, further comprising implementing a revised executable plan in response to "if . . . then" rules imposed on the input planning data.

6. A method according to claim 1, further comprising using the planning engine for generating the executable plan and controlled by a planning calendar.

7. A method according to claim 6, further comprising changing the planning calendar to accommodate at least one of scheduling a new planning event, changing the time of a planning event, and eliminating a previously scheduled planning event.

8. A method according to claim 1, wherein said monitoring and utilizing comprises monitoring and utilizing said input planning data in an operational planning mode for determining if the executable plan is to be revised immediately.

9. A method according to claim 1, wherein said monitoring and utilizing comprises monitoring and utilizing said input planning data in a strategic planning mode for determining an optimal time to revise the executable plan.

10. A method according to claim 1, comprising implementing the method in a computer.

18. A method according to claim 7, wherein the planning event comprises a shipment of a product.

11. A computerized proactive planning system comprising:

1) a planning engine for analyzing planning information and generating an executable plan upon the significance of a planning event, said planning information being derived by an automated process from real enterprise data;

2) a data base connected to the planning engine comprising planning information for input to the planning engine; and

3) a proactive planning driver connected to the data base comprising;

(i) means for detecting changes in the data base planning information;

(ii) means using said detected changes in the data base, for determining a time when a planning event should occur; and

(iii) means for communicating the timing of said planning event to the planning engine,

wherein depending upon said changes in the data base planing information, said determining means selectively determines if and/or when the executable plan is to be revised during a period of execution by said planning engine, such that depending upon a magnitude of said changes, as represented by said planning information, to said executable plan, said planning engine is selectively employed.

12. A proactive planning system according to claim 11, wherein said proactive planning driver further comprises a planning engine for generating a candidate plan and a plan comparer.

13. A computer-implemented method for using a proactive planning system, which method comprises:

1) providing a proactive planning system, the system including;

(i) a planning engine for analyzing planning information and generating an executable plan upon the signification of a planning event, said planning data being derived by an automated process from real enterprise data;

(ii) at least one data base connected to the planning engine, the each said at least one data base comprising planning information for input to the planning engine;

(iii) a proactive planning driver connected to the each at least one data base comprising;

(1) means for detecting changes in the each at least one data base planning information;

(2) means, using said detected changes in the each at least one data base, for determining a time when a planning event should occur; and

(3) means for communicating the timing of said planning event to the planning engine; and

(2) monitoring information input to the planning system;

(3) using information input to the planning system selectively for determining if and/or when the executable plan is to be revised, such that depending upon a magnitude of said changes, as represented by said planning information, to said executable plan, said planning engine is selectively employed; and

4) allocating resources based on said determining.

14. A method according to claim 13, further comprising displaying, conditioned upon determining that the executable plan is to be revised, an output of the planning engine to an operator.

15. A method according to claim 13, further comprising transmitting, conditioned upon determining that the executable plan is to be revised, an output of the planning engine to an execution system.

16. A method according to claim 13, further comprising:

3) analyzing each of one or more changes to the databases;

4) determining an interval of time in a planning horizon that is affected by the change in data;

5) subtracting the time required to execute the planning event from this interval of time to compute a date d; and

6) scheduling a new planning event to take place at date d.

17. A method according to claim 13, further comprising:

3) inputting to the planning engine from the each said at least one data base planning information comprising changed data;

4) running the planning engine for generating a new plan;

5) comparing the new plan to the executable plan for determining an interval in a planning horizon at which the new plan and the executable plan diverge;

6) subtracting the time required to execute the planning process from this interval of time for computing a date d; and

7) scheduling a new planning event to take place at date d.