System and method for scheduling linked events with fixed and dynamic conditions

• US 5,692,125 A
• Filed: 05/09/1995
• Issued: 11/25/1997
• Est. Priority Date: 05/09/1995
• Status: Expired due to Term

• Current Assignee: Uniloc 2017 LLC (SoftBank Group Corp.)
• Original Assignee: International Business Machines Corporation
• Inventors: Tetzlaff, Linda Sue, Schloss, Robert Jeffrey
• Primary Examiner(s): Hayes, Gail O.
• Assistant Examiner(s): Poinvil, Frantzy
• Application Number:
  US08/438,153
• Time in Patent Office: 931 Days
• Field of Search: 395/201, 395/208, 395/209, 395/672, 395/673, 395/670, 395/963, 434/108, 364/468.01
• US Class Current: 705/7.16
• 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/063116 Schedule adjustment for a person or group
• 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/1093 Calendar-based scheduling for persons or groups
• CPC Class Codes: G06Q 10/1097 Task assignment

Abstract

In a scheduling system, events and/or groups of events are checked at a scheduling time to insure that certain fixed conditions associated with the event(s) are satisfied. The events are also checked at one or more times, between scheduling time and a performance time (when the event(s) are to be performed), called "prepare to perform time(s)." At the prepare to perform time(s), certain dynamic conditions and/or data associated with the events are checked to determine whether the dynamic conditions are satisfied. If the dynamic conditions are satisfied, the event(s) are confirmed for performance. If one or more of the dynamic conditions are not satisfied, the event(s) are modified. Events can be modified by cancelling, altering or postponing. When an event(s) is modified, a notification can be sent out. Further, a modification of a event(s) can cause modifications to one or more subsequent events in the event group (propagation.) Templates are event groups with some omitted information that is provided by a user at scheduling time. Templates are used to facilitate the scheduling of common events and/or event groups.

Claims

1. A scheduling system for scheduling events, comprising:

a. a computer with a central processing unit and a memory;

b. one or more events to be scheduled and each event stored in the memory as an event data structure, one or more of the events having one or more event conditions, the event conditions defined in the respective event data structure and the event conditions being satisfied before the event can be performed;

c. one or more links, each link connecting two or more events, each link identified in one or more of the event data structures of the respective events that the link connects and each link establishing sequential relationships between the events that the link connects; and

d. a scheduler executed by the central processing unit to schedule one or more event groups, each event group having one or more events connected by one or more of the links, the scheduler scheduling the event group only if all of the event conditions in the event group are satisfied.

2. A scheduling system, as in claim 1, wherein one or more the event conditions is not satisfied, each of the unsatisfied event conditions having an associated adjustment rule, and the associated adjustment rule being applied for each unsatisfied event condition to modify the event so that the event can be performed.

3. A scheduling system, as in claim 2, wherein applying one or more of the adjustment rules alters the event.

4. A scheduling system, as in claim 2, wherein applying one or more of the adjustment rules reschedules the event.

5. A scheduling system, as in claim 1, wherein one or more event conditions is not satisfied and a message is sent to a user.

6. A scheduling system, as in claim 1, wherein the event conditions include one or more fixed conditions and the event is performed by scheduling of the event at an event scheduling time when the fixed conditions are satisfied.

7. A scheduling system, as in claim 1, wherein the event conditions include one or more dynamic conditions and the event is performed by reminding a user of the event at a performance time, the event being scheduled at a schedule time, if the dynamic conditions are satisfied at one or more prepare-to-perform-times.

8. A scheduling system, as in claim 1, wherein the event conditions include dynamic conditions which, if not satisfied at one or more prepare-to-perform-times, cause one or more events to be modified in any one of the following ways:

cancel, reschedule, and alter.

9. A scheduling system, as in claim 1, wherein one or more new events can be connected to one or more events in the event group with one or more links.

10. A scheduling system, as in claim 1, wherein two event groups are sequentially connected together by a link to produce a new event group.

11. A scheduling system, as in claim 10, wherein the new event group is scheduled on an electronic calendar.

12. A scheduling system for scheduling events, as in claim 1, wherein the events describe activities in any one of the following domains:

finance, accounting, banking, marketing, telemarketing, construction, and manufacturing.

13. A scheduling system for scheduling events, comprising:

a. a computer with a central processing unit, a memory, and an electronic calendar;

b. one or more events to be scheduled on the electronic calendar, each event being described in an event data structure stored in the memory, the data structure having one or more event conditions associated with respective event described in the event data structure, the event conditions being zero or more fixed conditions and zero or more dynamic conditions, the fixed conditions being satisfied before the event can be scheduled on the electronic calendar at a schedule time and dynamic conditions being satisfied at a prepare-to-perform-time before the event can be performed at a performance time;

c. one or more links, each link connecting two or more events, and each link establishing sequential relationships between the events that the link connects and each link establishing an interval wait condition between the evens;

d. one or more event groups, each event group having one or more events connected by one or more of the links;

e. a template representation of each of the event groups, the template having one or more variables that include sequential information that defines the sequential relationship of the events, the template further having omitted information; and

f. a process, executed by the central processing unit, for scheduling every event in a template representation when the omitted information is provided by a user.

14. A scheduling system, as in claim 13, wherein the omitted information is a template start time.

15. A scheduling system, as in claim 13, wherein one or more of the events is associated with event-additional-information about the event.

16. A scheduling system, as in claim 15, wherein the event additional information is operated on by event rules to evaluate a condition.

17. A scheduling system, as in claim 15, wherein the event-additional-information is provided by a user and a notification is given to the user based on the event-additional-information provided.

18. A scheduling system, as in claim 15, wherein the event information is audit information.

19. A scheduling system, as in claim 16, wherein the event additional information includes an event repetition count and an event repetition interval which causes the event to be scheduled the number of times specified by the count, each scheduled time separated by the repetition interval.

20. A scheduling system for scheduling medical events, comprising:

a. a computer with a central processing unit and a memory;

b. one or more of the medical events to be scheduled, each medical event stored in the memory as an event data structure and one or more of the medical events having one or more associated medical event conditions, the medical event conditions defined in the respective event data structure and the medical event conditions being satisfied before the medical event can be performed;

c. one or more links, each link connecting two or more of the medical events, and each link establishing sequential relationships between the medical events that the link connects; and

d. a scheduler executed by the central processing unit that schedules one or more medical event groups, each medical event group having one or more of the medical events connected by one or more of the links, the medical event group scheduled only if all of the medical event conditions in the medical event group are satisfied.

21. A scheduling system for scheduling events, comprising:

a. a computer means with a memory means for storing one or more event means;

b. one or more link means for connecting two or more of the event means, and each link means establishing sequential relationships between the event means that the link means connects;

c. one or more fixed condition means for permitting one or more of the event means to be scheduled at a schedule time if the fixed condition means is satisfied; and

d. one or more dynamic condition means for permitting one or more of the event means to be scheduled at a performance time if the dynamic conditions means are satisfied at one or more prepare-to-perform-times.

22. A method executing on a computer for scheduling comprising the steps of:

a. at a schedule time, examining a tentative start time of one or more events, each event being connected to one or more other events by a link, each link establishing a sequential relationship between the events that the link connects, the connected events forming an event group;

b. determining if the tentative start time is an illegal time;

c. if the tentative start time is an illegal time, applying one or more adjustment rules to the tentative start time to produce a new tentative start time;

d. replacing the tentative start time with the new tentative start time;

e. repeating steps b through e until the tentative start time is a legal start time for the event; and

f. scheduling the event at the legal start time.

23. A method, as in claim 22, further comprising the following steps:

g. checking, at one or more prepare-to-perform-times, if one or more dynamic conditions associated with one or more of the events is satisfied;

h. if one of the dynamic conditions is not satisfied, determining if the event should be cancelled as specified by the adjustment rules;

i. if the event is to be cancelled, notify a user;

j. if the event is not to be cancelled, rescheduling the event if rescheduling is specified by the adjustment rules;

k. if the event is not to be cancelled or rescheduled, altering the event if altering is specified by the adjustment rules; and

l. if the event is not to be cancelled, altering and rescheduling the event if altering and rescheduling is specified by the adjustment rules.

24. A method, as in claim 23, further comprising the step of:

m. propagating the effect of modifying an event through out the event group where the modification to the event includes any one of the following;

cancellation and rescheduling.