Distributed activity management

• US 20070276715A1
• Filed: 05/15/2007
• Published: 11/29/2007
• Est. Priority Date: 05/15/2006
• Status: Abandoned Application

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Beringer, Joerg, Moore, Dennis
• Application Number:
  US11/803,760
• Publication Number:
  US 20070276715A1
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 10/0633 Workflow analysis
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Methods and apparatuses enable generating distributed workflows that couple actions with a business scenario, and relate activities to each other with request-to-perform (RTP) relationships. The activities are coupled to the business scenario to generate a workflow, and the RTP relationships enable management of distributed activities that are part of the workflow. Individual actions and activities that are part of a business objective are modeled. The modeled actions define resources related to a business activity. The individual activities can be instantiated and related with RTP relationships to result in a workflow that can be generated and managed by the enterprise system. Interactions between users can be captured within the system as part of the workflow. In one embodiment, distributed workflows operate within traditional fixed (e.g., ERP) workflows, for example, by modeling complex tasks of a fixed workflow that actually requires multiple actions before being completed.

Claims

1. A method for modeling a business process, comprising:

generating a first activity of a workflow from one or more work action templates of a backend enterprise system, the generating including providing a parameter to associate the first activity with a business scenario;

generating a second activity of a workflow from one or more work action templates of the backend enterprise system, the generating including providing a parameter to define a relationship of the second activity with a business scenario; and

relating the first and second activities via a request-to-perform relationship.

6. The method of claim 1, wherein relating the activities comprises:

relating human-to-human actions via the request-to-perform relationship.

2-5. -5. (canceled)

7-21. -21. (canceled)

22. A method for modeling a business process, comprising:

instantiating from a template in a backend enterprise system a fixed workflow having a series of multiple tasks, at least one of the tasks being a complex task having multiple activities, each task of the fixed workflow being a state of the fixed workflow, where state changes in the fixed workflow are based on a transactional control;

instantiating from a template in the backend enterprise system a distributed workflow for the complex task, the distributed workflow having an activity context containing the multiple activities and resources associated with the complex task, each activity being a state of the distributed workflow, where state changes in the distributed workflow are based on a request-to-perform control; and

monitoring the fixed workflow and the distributed workflow with the backend enterprise system.

23. The method of claim 22, wherein generating the fixed workflow comprises:

generating an enterprise resource planning (ERP) workflow from a database of ERP workflows.

24. The method of claim 22, wherein the transaction control comprises completion of a task that represents a transaction of the fixed workflow.

25. The method of claim 22, wherein the request-to-perform control comprises generation of a request for performance of an activity by another entity.

26. A system comprising:

a nonvolatile storage device having stored thereon a template that defines a fixed workflow having a series of multiple tasks, at least one of the tasks being a complex task having multiple activities, each task of the fixed workflow being a state of the fixed workflow, where state changes in the fixed workflow are based on a transactional control; and

a template that defines a distributed workflow for the complex task, the distributed workflow having an activity context containing the multiple activities and resources associated with the complex task, each activity being a state of the distributed workflow, where state changes in the distributed workflow are based on a request-to-perform control; and

a memory device coupled to the nonvolatile storage device in which to instantiate the fixed workflow and the distributed workflow from the templates, the memory device further including a workflow monitor to manage the fixed workflow and the distributed workflow, including documenting the state changes in the fixed workflow and the state changes in the distributed workflow.

27. A method for modeling a business process, comprising:

generating a business scenario description defining human interactions to accomplish a business purpose;

defining the business scenario description as multiple activities to be distributed to various performers;

generating an activity description defining an activity as one or more actions to be accomplished by a single performer;

associating one or more activity descriptions to the business scenario description;

associating one or more resources with the business scenario description, the resources to be passed to and returned from activity descriptions of the business scenario description; and

associating one or more resource with the activity description, the resources to be passed to and returned from the actions of the activity description.

28. The method of claim 27, wherein generating the activity description comprises:

generating an activity description applicable to multiple different business scenarios; and

storing the activity description as a reusable business activity building block for generating business process workflows.

29. The method of claim 27, wherein associating the one or more resources with the activity description comprises:

defining one or more of a document, a business object, or an enterprise service as a resource for the business activity.

30. The method of claim 27, further comprising:

generating an action description applicable to multiple different business activities; and

storing the action description as a reusable business action building block for generating business process workflows.

31. The method of claim 27, further comprising:

relating the activity description to another activity description to generate a workflow for the business process.

32. The method of claim 31, wherein relating the activity descriptions comprises:

relating human-to-human actions via a request-to-perform relationship.

33. The method of claim 27, further comprising:

monitoring the one or more actions of the business activity via a backend enterprise system.

34. The method of claim 33, wherein monitoring one or more actions via the backend enterprise system comprises:

storing results generated from execution of the actions.

35. The method of claim 33, wherein monitoring one or more actions via the backend enterprise system comprises:

assigning a task to a different performer in response to performance of an action.

36. The method of claim 35, wherein assigning the task to the different performer further comprises:

transferring ownership of the business process in the backend system to the different performer via a transition from the activity to assigned task.

37. The method of claim 27, wherein monitoring one or more actions via the backend enterprise system comprises:

capturing human-to-human interaction as part of the business process.

38. An article of manufacture comprising a machine readable medium having content stored thereon to provide instructions to cause a machine to perform operations including:

generating a business scenario description defining a work context of human interactions to accomplish a business purpose, including defining activities to be distributed to various performers to accomplish the business purpose;

generating an activity description template defining a business activity for a performer, the activity description including a parameter configurable to define a one or more resources associated with the business activity;

generating a work action template defining work to be executed by the performer to accomplish a distributed activity;

generating an association between the action template and the activity description template, and an association between the activity description template and the business scenario description; and

storing the business scenario description, the activity description template, the action template, and the associations in an enterprise system.

39. The article of manufacture of claim 38, wherein the content to provide instructions for generating the templates comprises content to provide instructions for

generating reusable building block components from which a distributed workflow is created.

40. The article of manufacture of claim 38, wherein the content to provide instructions for generating the business activity template further comprises content to provide instructions for

generating the business activity template with associated metadata that defines a relationship of the business activity to the business scenario.

41. The article of manufacture of claim 38, further comprising content to provide instructions for

assigning a request-to-perform relationship between two business activities.

42. The article of manufacture of claim 41, wherein the content to provide instructions for assigning the request-to-perform relationship between the business activities further comprises content to provide instructions for

assigning an event trigger as a request.

43. The article of manufacture of claim 42, wherein the content to provide instructions for assigning the event trigger comprises content to provide instructions for

assigning as a request a human request or a self-initiated event.

44. The article of manufacture of claim 42, wherein the content to provide instructions for assigning the event trigger comprises content to provide instructions for

assigning as a request a business event, a system exception, or a task.

45. The article of manufacture of claim 38, wherein the content provides instructions for generating a distributed workflow for a business process associated with the business purpose.

46. The article of manufacture of claim 45, wherein the content provides instructions for generating a distributed workflow for all tasks of the business process.