# US 2004/0083448 A1 · Workflow management architecture

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2004/0083448 A1
- Document ID: US20040083448A1
- Status: Published application
- Kind: A1
- Application number: 10/628,565
- Filed: 2003-07-29
- Published: 2004-04-29
- Earliest claimed: 2002-07-31
- Assignees: Sap SE
- Inventors: Karsten Schulz; Maria E. Orlowska
- Web page: https://patentgrep.com/patent/US20040083448A1

## CPC

- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q 10/0633: Workflow analysis
- G06Q 10/103: {Workflow collaboration or project management}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A workflow model is described. In one example of the workflow model, a first workflow is associated with a first party, and a first workflow view is used to represent an abstraction of the first workflow. Similarly, a second workflow is associated with a second party, and a second workflow view is used to represent an abstraction of the second workflow. Then, a coalition workflow view referencing the first workflow view and the second workflow view provides a collaborative workflow that specifies tasks that the first party and the second party are required to perform. In this way, multiple parties may easily partner with one another to accomplish a business objective, while maintaining a level of confidentiality of their workflow processes.

## Claims

### Claim 1

A workflow model comprising:
a first workflow associated with a first party;
a first workflow view representing an abstraction of the first workflow;
a second workflow associated with a second party;
a second workflow view representing an abstraction of the second workflow; and
a coalition workflow view referencing the first workflow view and the second workflow view to provide a collaborative workflow, the collaborative workflow specifying tasks that the first party and the second party are required to perform.

### Claim 2 (depends on 1)

The workflow model of claim 1 wherein the first workflow and the second workflow are private to the first and second parties, respectively.

### Claim 3 (depends on 1)

The workflow model of claim 1 wherein the first workflow view comprises a first virtual task and a second virtual task corresponding to a first actual task and a second actual task, respectively, of the first workflow.

### Claim 4 (depends on 1)

The workflow model of claim 1 wherein the first virtual task corresponds to a first plurality of actual tasks of the first workflow, and the second virtual task corresponds to a second plurality of tasks of the second workflow.

### Claim 5 (depends on 4)

The workflow model of claim 4 further comprising a first set of dependencies between the first virtual task and the first plurality of actual tasks, and a second set of dependencies between the second virtual task and the second plurality of actual tasks, wherein the first and second set of dependencies are selected so as to maintain an order of operation of the first plurality of actual tasks relative to the second plurality of actual tasks.

### Claim 6 (depends on 4)

The workflow model of claim 4 wherein a first virtual execution state of the first virtual task corresponds to a first actual execution state of the first plurality of actual tasks.

### Claim 7 (depends on 6)

The workflow model of claim 6 wherein an actual state transition of the first actual execution state is reflected in a virtual state transition of the first virtual execution state.

### Claim 8 (depends on 6)

The workflow model of claim 6 wherein a message from the second party concerning the first virtual task is forwarded to an active task within the first plurality of actual tasks via the first virtual task, based on the first actual execution state.

### Claim 9 (depends on 3)

The workflow model of claim 3 wherein the second workflow view comprises a third virtual task and a fourth virtual task corresponding to a third actual task and a fourth actual task, respectively, of the second workflow.

### Claim 10 (depends on 9)

The workflow model of claim 9 wherein the tasks within the coalition workflow comprise the first virtual task, the second virtual task, the third virtual task, and the fourth virtual task.

### Claim 11 (depends on 10)

The workflow model of claim 10 wherein the tasks within the collaborative workflow further comprise a synchronizing task operable to preserve an order of execution of the first virtual task, the second virtual task, the third virtual task, and the fourth virtual task.

### Claim 12 (depends on 11)

The workflow model of claim 11 wherein the synchronizing task relates a finished execution state of the second virtual task to a beginning execution state of the third virtual task.

### Claim 13 (depends on 1)

The workflow model of claim 1 wherein the collaborative workflow is implemented by communications between the first party and the second party regarding the first workflow view and the second workflow view.

### Claim 14 (depends on 1)

The workflow model of claim 1 wherein the collaborative workflow is implemented by a third-party mediator facilitating communications between the first party and the second party.

### Claim 15 (depends on 1)

The workflow model of claim 1 comprising a third workflow view corresponding to a second abstraction of the first workflow and constructed for forming a second coalition workflow view referencing the third workflow view and a third workflow associated with a third party, to thereby provide a second collaborative workflow associated with the first party and the third party.

### Claim 16

A method comprising:
associating a first workflow associated with a first party with a first workflow view representing an abstraction of the first workflow;
associating a second workflow associated with a second party with a second workflow view representing an abstraction of the second workflow; and
including the first workflow view and the second workflow view within a coalition workflow view to provide a collaborative workflow, the collaborative workflow specifying tasks that the first party and the second party are required to perform.

### Claim 17 (depends on 16)

The method of claim 16 wherein the first workflow and the second workflow are private to the first and second parties, respectively.

### Claim 18 (depends on 16)

The method of claim 16 wherein associating the first workflow with the first workflow view comprises associating a first virtual task and a second virtual task of the first workflow view with a first actual task and a second actual task, respectively, of the first workflow.

### Claim 19 (depends on 18)

The method of claim 18 wherein associating the first workflow with the first workflow view comprises:
associating the first virtual task with a first plurality of actual tasks of the first workflow; and
associating the second virtual task with a second plurality of tasks of the second workflow.

### Claim 20 (depends on 19)

The method of claim 19 wherein associating the first workflow with the first workflow view comprises:
constructing a first set of dependencies between the first virtual task and the first plurality of actual tasks; and
constructing a second set of dependencies between the second virtual task and the second plurality of actual tasks,
wherein the first and second set of dependencies are selected so as to maintain an order of operation of the first plurality of actual tasks relative to the second plurality of actual tasks.

### Claim 21 (depends on 19)

The method of claim 19 wherein associating the first virtual task to the first plurality of actual tasks comprises associating a first virtual execution state of the first virtual task with a first actual execution state of the first plurality of actual tasks.

### Claim 22 (depends on 21)

The method of claim 21 further comprising reflecting an actual state transition of the first actual execution state in a virtual state transition of the first virtual execution state.

### Claim 23 (depends on 21)

The method of claim 21 further comprising forwarding a message from the second party concerning the first virtual task to an active task within the first plurality of actual tasks via the first virtual task, based on the first actual execution state.

### Claim 24 (depends on 18)

The method of claim 18 wherein associating the second workflow with the second workflow view comprises associating a third virtual task and a fourth virtual task of the second workflow view with a third actual task and a fourth actual task, respectively, of the second workflow.

### Claim 25 (depends on 24)

The method of claim 24, wherein including the first workflow view and the second workflow view within a coalition workflow view comprises including the first virtual task, the second virtual task, the third virtual task, and the fourth virtual task within the coalition workflow as the tasks within the coalition workflow.

### Claim 26 (depends on 25)

The method of claim 25 wherein including the first workflow view and the second workflow view within a coalition workflow view comprises including a synchronizing task operable to preserve an order of execution of the first virtual task, the second virtual task, the third virtual task, and the fourth virtual task within the coalition workflow as the tasks within the coalition workflow.

### Claim 27 (depends on 26)

The method of claim 26 wherein including a synchronizing task comprises relating a finished execution state of the second virtual task to a beginning execution state of the third virtual task.

### Claim 28 (depends on 16)

The method of claim 16 wherein including the first workflow view and the second workflow view within a coalition workflow view comprises communicating between the first party and the second party regarding the first workflow view and the second workflow view, to thereby implement the collaborative workflow.

### Claim 29 (depends on 16)

The method of claim 16 wherein the collaborative workflow is implemented by a third-party mediator facilitating communications between the first party and the second party.

### Claim 30 (depends on 16)

The method of claim 16 further comprising:
associating a third workflow view with a second abstraction of the first workflow; and
forming a second coalition workflow view referencing the third workflow view and a third workflow associated with a third party, to thereby provide a second collaborative workflow associated with the first party and the third party.

### Claim 31

A system comprising:
a first workflow modeler operable to model a first workflow associated with a first party;
a first view modeler operable to model a first virtual workflow as an abstraction of the first workflow; and
a workflow engine operable to execute the first workflow and to virtually execute the first virtual workflow in conjunction with a second workflow associated with a second party.

### Claim 32 (depends on 31)

The system of claim 31 wherein the workflow engine is operable to execute the first virtual workflow in conjunction with a second virtual workflow, wherein the second virtual workflow is an abstraction of the second workflow.

### Claim 33 (depends on 31)

The system of claim 31 wherein the first virtual workflow comprises a first virtual task associated with a first task and a second task of the first workflow, and further wherein the workflow engine is operable to associate a virtual execution state of the first virtual task with a first execution state of the first task and a second execution state of the second task.

### Claim 34 (depends on 33)

The system of claim 33 further comprising a monitor operable to track the virtual execution state, the first execution state, and the second execution state.

### Claim 35 (depends on 31)

The system of claim 31 further comprising a database for storing the first workflow, instances of the first workflow, the first virtual workflow, and instances of the first virtual workflow.

### Claim 36 (depends on 31)

The system of claim 31 further comprising a gateway operable to route messages to and from the second party and the workflow engine, the messages concerning the first virtual workflow and the second workflow.

### Claim 37 (depends on 31)

The system of claim 31 further comprising a mediator operable to mediate interactions between the first virtual workflow and the second workflow, the mediator comprising:
a security manager operable to receive messages regarding the first virtual workflow for decryption;
a database operable to store the first virtual workflow, the second workflow, instances of the first virtual workflow, and instances of the second workflow; and
a monitor operable to track execution states of the first virtual workflow and the second workflow.
