VIGIP006 - collaborative resolution and tracking of detected events

• US 20030018643A1
• Filed: 06/19/2002
• Published: 01/23/2003
• Est. Priority Date: 06/19/2001
• Status: Abandoned Application

• Current Assignee: Infor Global Solutions Chicago Incorporated (Infor Incorporated)
• Original Assignee: Infor Global Solutions Chicago Incorporated (Infor Incorporated)
• Inventors: Tantry, Subhash B., Mi, Peiwei, Cooray, Manoj P.B., Lo, Chien-Ju
• Application Number:
  US10/176,282
• Publication Number:
  US 20030018643A1
• Time in Patent Office: Days
• US Class Current: 707/10
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Methods and apparatus are disclosed for collaboratively tracking and resolving detected events and conditions, which are referred to as Exceptions. Through one or more forms, users may interact to collaboratively resolve and track the resolution of detected events and conditions. A user may choose to take a more active role and resolve a detected event through a user exit that is previously defined, which provides an action (e.g., procedure or function to another external application) that can be initiated by a user to resolve a detected event. In addition, once an event is detected and an exception has been generated, the original source data that triggered the exception may continue to be monitored so that the exception is updated accordingly. When an exception has been updated, it may be desirable to escalate and notify one or more individuals of the change in the exception. This notification may be accomplished through the monitoring of an exception using an escalation rule that detects a change (or non-change) in one or more field values (e.g., status) of the exception. Finally, correspondences with regard to the detected event are organized in a web site and displayed to users in a fashion that is similar to an Internet discussion group.

Claims

1. A method of maintaining data associated with a detected event, comprising:

maintaining data related to the detected event;

providing the data related to the detected event such that the data related to the detected event can be viewed by a set of one or more individuals; and

maintaining one or more collaboration entries, each of the one or more collaboration entries being from one of the set of one or more individuals and including information associated with the detected event.

2. The method as recited in claim 1, further comprising:

at least one of receiving and updating one of the collaboration entries.

3. The method as recited in claim 2, wherein the one of the collaboration entries indicates a function or procedure has been executed for resolution of the detected event.

4. The method as recited in claim 2, wherein the one of the collaboration entries has an associated function or procedure to be executed for resolution of the detected event.

5. The method as recited in claim 2, wherein the one of the collaboration entries comprises a function or procedure to be executed for resolution of the detected event.

6. The method as recited in claim 2, further comprising:

selecting a form via which the collaborative entry is to be entered.

7. The method as recited in claim 6, wherein selecting the form via which the collaborative entry is to be entered comprises:

selecting one of the collaborative entries to which the collaborative entry is to reply, thereby enabling the collaborative entry to be linked to the selected one of the collaborative entries.

8. A method of monitoring data associated with a detected event, comprising:

maintaining data related to the detected event, the data being obtained from a data source from which the event was detected;

monitoring the data source for satisfaction of one or more rules with respect to the detected event; and

updating the data related to the detected event when the one or more rules are satisfied.

9. The method as recited in claim 8, wherein updating the data related to the detected event comprises:

updating one or more status values associated with the detected event in accordance with the satisfied rules.

10. The method as recited in claim 8, further comprising:

monitoring the data related to the detected event for satisfaction of a second set of one or more rules with respect to the detected event; and

sending a message to one or more individuals indicating the satisfaction of the second set of one or more rules with respect to the detected event.

11. The method as recited in claim 10, wherein the first set of rules is different from the second set of rules.

12. The method as recited in claim 10, wherein the first set of rules is the same as the second set of rules.

14. The method as recited in claim 9, wherein the satisfaction of one or more rules with respect to the detected event indicates a change in the data related to the detected event.

15. The method as recited in claim 13, wherein monitoring the data related to the detected event for satisfaction of one or more rules with respect to the detected event comprises:

detecting a change in one or more status values associated with the detected event.

17. The method as recited in claim 16, wherein the one or more criteria comprise at least one of time, priority, and customer.

18. The method as recited in claim 16, wherein providing the distribution of the data in accordance with a selected format.

19. The method as recited in claim 18, wherein the selected format is one of pie chart, bar chart, and distribution over time line chart.

20. The method as recited in claim 16, further comprising:

receiving a selection of the one or more criteria over which the data is to be distributed and provided.

13. A method of monitoring data associated with a detected event, comprising:

maintaining data related to the detected event;

monitoring the data related to the detected event for satisfaction of one or more rules with respect to the detected event; and

sending a message to one or more individuals indicating the satisfaction of one or more rules with respect to the detected event.

16. A method of maintaining data associated with a detected event, comprising:

maintaining data related to one or more detected events;

determining a distribution of the data related to the detected events across one or more criteria; and

providing the distribution of the data related to the detected events across one or more criteria such that the data related to the detected event can be viewed by a set of one or more individuals.