# US 2012/0084215 A1 · Electronic Process-Driven Collaboration System

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

- Number: US 2012/0084215 A1
- Document ID: US20120084215A1
- Status: Published application
- Kind: A1
- Application number: 13/039,291
- Filed: 2011-03-02
- Published: 2012-04-05
- Earliest claimed: 2010-10-05
- Assignees: Accenture Global Services Limited
- Inventors: David E. Trier; Michael A. Holzman; Louis Charles Nebolsky; Fausto A. Inestroza
- Web page: https://patentgrep.com/patent/US20120084215A1

## CPC

- G06Q 10/10: Office automation; Time management
- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- 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 business process-driven collaboration system embeds collaboration resources and tools directly into existing business processes and applications. The system interfaces with an existing business process management (BPM) service to extract dynamic metadata and an activity identifier associated with a current business process. The system obtains static metadata based on the activity identifier from a collaboration template. The system also merges the static and dynamic metadata, and provides the merged metadata to a process-driven collaboration service to be used in embedding collaboration utilities into the existing business applications.

## Claims

### Claim 1

A process-driven collaboration system for integration into a business process management system, comprising:
a processor;
a memory coupled to the processor, the memory comprising:
at least one collaboration template comprising:
multiple activity identifiers, wherein each activity identifier corresponds with a business activity of a business process associated with the business process management system; and
static metadata associated with each activity identifier;
instructions that, when executed, cause the processor to:
obtain an activity identifier corresponding to a current business process activity of the business process;
extract dynamic metadata from the business process management system corresponding to the current business process activity;
obtain static metadata from the at least one collaboration template based on the obtained activity identifier corresponding to the current business process activity;
merge the dynamic and static metadata; and
transmit the merged metadata to a process-driven collaboration service.

### Claim 2 (depends on 1)

The system of claim 1, wherein obtaining an identification of a current business process activity comprises:
determining whether a business software application associated with the business process provides the activity identifier corresponding to the current business process activity; and
based on a determination that the business software application does not provide the activity identifier corresponding to the current business process activity, extracting the activity identifier corresponding to the current business process activity from the business process management system.

### Claim 3 (depends on 1)

The system of claim 1, wherein the at least one collaboration template further comprises an identification of at least one recommended business activity associated with each of the activity identifiers.

### Claim 4 (depends on 3)

The system of claim 3, wherein the instructions, when executed, further cause the processor to:
obtain at least one recommended business activity from the at least one collaboration template based on the obtained activity identifier corresponding to the current business process activity; and
transmit the obtained at least one recommended business activity along with the merged metadata to the process-driven collaboration service.

### Claim 5 (depends on 1)

The system of claim 1, wherein the static metadata comprises a list of at least one searchable keyword associated with the corresponding activity identifier.

### Claim 6 (depends on 1)

The system of claim 1, wherein the instructions, when executed, further cause the processor to determine whether the current activity of the business process has changed.

### Claim 7 (depends on 6)

The system of claim 6, wherein based on a determination that the current activity of the business process has changed to a new current activity, the instructions further cause the processor to:
obtain a new activity identifier corresponding to the new current activity;
obtain new static metadata corresponding to the new activity identifier;
extract new dynamic metadata corresponding to the new current activity;
merge the static and new dynamic metadata into new merged metadata;
transmit the new merged metadata to a process-driven collaboration service.

### Claim 8

A process-driven collaboration system for integration into a business process management system, comprising:
a processor;
a memory coupled to the processor, the memory comprising instructions that, when executed, cause the processor to:
obtain an activity identifier corresponding to a current business process activity of the business process;
extract dynamic metadata from the business process management system corresponding to the current business process activity;
obtain static metadata from at least one collaboration template based on the obtained activity identifier;
merge the dynamic and static metadata; and
transmit the merged metadata to a process-driven collaboration service.

### Claim 9 (depends on 8)

The system of claim 8, wherein obtaining an identification of a current business process activity comprises:
determining whether a business software application associated with the business process provides the activity identifier corresponding to the current business process activity; and
based on a determination that the business software application does not provide the activity identifier corresponding to the current business process activity, extracting the activity identifier corresponding to the current business process activity from the business process management system.

### Claim 10 (depends on 8)

The system of claim 8, wherein the at least one collaboration template comprises:
multiple activity identifiers, wherein each activity identifier corresponds with a business activity of a business process associated with the business process management system; and
static metadata associated with each activity identifier.

### Claim 11 (depends on 10)

The system of claim 10, wherein the at least one collaboration template further comprises an identification of at least one recommended business activity associated with each of the activity identifiers.

### Claim 12 (depends on 11)

The system of claim 11, wherein the instructions, when executed, further cause the processor to:
obtain at least one recommended business activity from the at least one collaboration template based on the obtained activity identifier corresponding to the current business process activity; and
transmit the obtained at least one recommended business activity along with the merged metadata to the process-driven collaboration service.

### Claim 13 (depends on 8)

The system of claim 8, wherein the static metadata comprises a list of at least one searchable keyword associated with the corresponding activity identifier.

### Claim 14 (depends on 8)

The system of claim 8, wherein the instructions, when executed, further cause the processor to determine whether the current activity of the business process has changed.

### Claim 15 (depends on 14)

The system of claim 14, wherein based on a determination that the current activity of the business process has changed to a new current activity, the instructions further cause the processor to:
obtain a new activity identifier corresponding to the new current activity;
obtain new static metadata corresponding to the new activity identifier;
extract new dynamic metadata corresponding to the new current activity;
merge the new static and new dynamic metadata into new merged metadata;
transmit the new merged metadata to a process-driven collaboration service.

### Claim 16

A method for integration process-driven collaboration into a business process management system, comprising:
obtaining, using a process-driven collaboration computer processor, an activity identifier corresponding to a current business process activity of the business process;
extracting, using the processor, dynamic metadata from the business process management system corresponding to the current business process activity;
obtaining, using the processor, static metadata from at least one collaboration template based on the obtained activity identifier;
merging, using the processor, the dynamic and static metadata; and
transmitting the merged metadata to a process-driven collaboration service.

### Claim 17 (depends on 16)

The method of claim 16, wherein obtaining an identification of a current business process activity comprises:
determining whether a business software application associated with the business process provides the activity identifier corresponding to the current business process activity; and
based on a determination that the business software application does not provide the activity identifier corresponding to the current business process activity, extracting the activity identifier corresponding to the current business process activity from the business process management system.

### Claim 18 (depends on 16)

The method of claim 16, wherein the at least one collaboration template comprises:
multiple activity identifiers, wherein each activity identifier corresponds with a business activity of a business process associated with the business process management system; and
static metadata associated with each activity identifier.

### Claim 19 (depends on 18)

The method of claim 18, wherein the at least one collaboration template further comprises an identification of at least one recommended business activity associated with each of the activity identifiers.

### Claim 20 (depends on 19)

The method of claim 19, further comprising:
obtaining at least one recommended business activity from the at least one collaboration template based on the obtained activity identifier corresponding to the current business process activity; and
transmitting the obtained at least one recommended business activity along with the merged metadata to the process-driven collaboration service.

### Claim 21 (depends on 16)

The method of claim 16, further comprising determining whether the current activity of the business process has changed.

### Claim 22 (depends on 21)

The method of claim 21, further comprising, responsive to a determination that the current activity of the business process has changed to a new current activity:
obtaining a new activity identifier corresponding to the new current activity;
obtaining new static metadata corresponding to the new activity identifier;
extracting new dynamic metadata corresponding to the new current activity;
merging the static and new dynamic metadata into new merged metadata;
transmitting the new merged metadata to a process-driven collaboration service.
