System and method for improving operational efficiency through process automation

• US 20030074090A1
• Filed: 02/13/2002
• Published: 04/17/2003
• Est. Priority Date: 09/28/2001
• Status: Abandoned Application

• Current Assignee: Intersect Software Corp.
• Original Assignee: Intersect Software Corp.
• Inventors: Yost, Michael Baker, Becka, Zdenek, Silton, Roderick Peter, Safa, Borna, Gorur, Ravi Srinath
• Application Number:
  US10/073,141
• Publication Number:
  US 20030074090A1
• Time in Patent Office: Days
• US Class Current: 700/83
• 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/10 Office automation; Time management

Abstract

The present invention addresses the aforementioned needs by providing a mechanism that improves operational efficiency through process automation. In one embodiment, process automation is enabled through rules that can be bound to system objects.

Claims

1. A method for enabling work automation, comprising:

displaying a first user interface that enables a user to define an automation rule, said automation rule including a specification of an event and an action; and

displaying a second user interface that enables a user to bind said automation rule to an event source, said binding enabling said automation rule to listen for events generated by said event source, wherein upon an occurrence of said event said action is carried out.

2. The method of claim 1, wherein said event is one of a system object attribute change, a system object association change, a timer expiration, a system object delete, a problem domain specific event, and an external event.

3. The method of claim 1, wherein said automation rule further includes a specification of a condition.

4. The method of claim 1, wherein said action is one of a create, update, bind, unbind, copy, execute, and notify actions.

5. The method of claim 1, wherein said event source is one of an activity, container, contract, resource and external system.

6. A method for enabling work automation, comprising:

defining an automation rule, said automation rule including a specification of an event and an action;

binding said automation rule to a first event source such that said automation rule listens for events generated by said first event source; and

binding said automation rule to a second event source such that said automation rule listens for events generated by said second event source,

wherein at least part of a behavior of said automation rule is defined by a particular event source to which it is bound.

7. The method of claim 6, wherein said events include a system object attribute change, a system object association change, a timer expiration, a system object delete, problem domain specific event, and an external event.

8. The method of claim 6, wherein said automation rule further includes a specification of a condition.

9. The method of claim 6, wherein said action is one of a create, update, bind, unbind, copy, execute, and notify actions.

10. The method of claim 6, wherein said event source is one of an activity, container, contract, resource and external system.

11. A user interface that enables work automation, said user interface comprising:

a first interface portion that is configured to enable selection of an automation rule, said automation rule including a specification of an event and an action; and

a second interface portion that is configured to display an event source icon that is associated with an event source,

wherein said user interface enables a user-controlled action of creating an association between said selected automation rule and said event source associated with said event source icon in said second interface portion, said user-controlled action initiating a binding of said automation rule to said event source, thereby enabling said automation rule to listen for events generated by said event source, wherein upon an occurrence of said event said action is carried out.

12. The user interface of claim 11, wherein said first interface portion includes a rule icon that is associated with said automation rule, said rule icon capable of being dragged to said event source icon.

13. The user interface of claim 11, wherein said first interface portion is a pop-up window.

14. The user interface of claim 11, wherein said event is one of a system object attribute change, a system object association change, a timer expiration, a system object delete, a problem domain specific event, and an external event.

15. The user interface of claim 11, wherein said automation rule further includes a specification of a condition.

16. The user interface of claim 11, wherein said action is one of a create, update, bind, unbind, copy, execute, and notify actions.

17. The user interface of claim 11, wherein said event source is one of an activity, container, contract, resource and external system.

18. A computer program product, comprising:

computer-readable program code for causing a computer to display a first user interface that enables a user to define an automation rule, said automation rule including a specification of an event and an action;

computer-readable program code for causing a computer to display a second user interface that enables a user to bind said automation rule to an event source, said binding enabling said automation rule to listen for events generated by said event source, wherein upon an occurrence of said event said action is carried out; and

a computer-usable medium configured to store the computer-readable program codes.

19. A computer program product, comprising:

computer-readable program code for causing a computer to define an automation rule, said automation rule including a specification of an event and an action;

computer-readable program code for causing a computer to bind said automation rule to a first event source such that said automation rule listens for events generated by said first event source;

computer-readable program code for causing a computer to bind said automation rule to a second event source such that said automation rule listens for events generated by said second event source,

wherein at least part of a behavior of said automation rule is defined by a particular event source to which it is bound; and

a computer-usable medium configured to store the computer-readable program codes.

20. A method for enabling work automation, comprising:

defining a portable automation rule, said portable automation rule including a specification of an event and an action; and

storing said defined portable automation rule in a rule repository, wherein said defined portable automation rule is capable of being individually bound to a plurality of event sources.

21. The method of claim 20, wherein said event includes one of a system object attribute change, a system object association change, a timer expiration, a system object delete, a problem domain specific event, and an external event.

22. The method of claim 20, wherein said automation rule further includes a specification of a condition.

23. The method of claim 20, wherein said action is one of a create, update, bind, unbind, copy, execute, and notify actions.

24. The method of claim 20, wherein an event source is one of an activity, container, contract, resource and external system.

25. A method for enabling work automation, comprising:

defining a workflow activity, said defined workflow activity including a series of steps and conditions for progressing through said series of steps; and

assigning said workflow activity from a workflow activity assignor to a workflow activity recipient, said workflow activity capable of being represented by an icon on a computer display of said workflow activity recipient.

26. The method of claim 25, wherein said workflow activity further comprises an automation function that is responsive to events and conditions.

27. A method for enabling work automation, comprising:

defining a portable workflow activity, said defined portable workflow activity including a series of steps and conditions for progressing through said series of steps; and

assigning said portable workflow activity from a workflow activity assignor to a workflow activity recipient, wherein at least part of a behavior of said assigned portable workflow activity is dependent on an environment in which said portable workflow activity operates.

28. The method of claim 27, wherein said workflow activity further comprises an automation function that is responsive to events and conditions.

29. A method for enabling work automation, comprising:

storing a personal rule binding that has been defined by a user, said personal rule binding identifying one or more automation rules that are to be automatically associated with a system object upon the creation of a particular user-object relationship;

determining whether an association of a user to a particular object matches said user-object relationship definition associated with said personal rule binding; and

upon said determination, binding said one or more automation rules to said particular object, thereby enabling said one or more automation rules to listens for events generated by said particular object.

30. The method of claim 29, wherein said user-object relationship identifies a particular object that said user is associated with.

31. The method of claim 29, wherein said user-object relationship identifies a particular role for said user.