# US 2007/0129976 A1 · Apparatus and methods for process and project management and control

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

- Number: US 2007/0129976 A1
- Document ID: US20070129976A1
- Status: Published application
- Kind: A1
- Application number: 10/551,353
- Filed: 2005-08-04
- Published: 2007-06-07
- Earliest claimed: 2005-08-04
- Assignees: Prolify Ltd.
- Inventors: Alon Hochberg; Vladimir Morgenstern
- Web page: https://patentgrep.com/patent/US20070129976A1

## CPC

- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q 10/063: Operations research, analysis or management
- G06Q 10/0631: Resource planning, allocation, distributing or scheduling for enterprises or organisations
- 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

An apparatus and method for project or process management and control. The apparatus and method are based on detailed task information, as obtained from miscellaneous sources, especially e-mail and other personal productivity tools. The apparatus and method create tasks and processes relevant for a project and provide real-time status information, analysis and additional derived tasks. The method is enabled by representing all the project-related information in a uniform way, such as a project map, and the usage of patterns of different types to represent all the knowledge about a task, a sub-project, or a project. The system identifies known patterns in the project map, adds derived actions, analyzed risky situations and generated notifications and alerts.

## Claims

### Claim 1

A method for constructing, controlling or managing a process, the method comprising the steps of:
transforming an at least one user event into an at least one block of uniform presentation; and
updating a project map with the uniform presentation block using an at least one pattern.

### Claim 2 (depends on 1)

The method of claim 1 further comprising the step of generating an at least one action.

### Claim 3 (depends on 2)

The method of claim 2 wherein the at least one action is to be assigned or notified to an at least one user.

### Claim 4 (depends on 2)

The method of claim 2 further comprising the steps of:
converting user data into the at least one user event; and
converting the at least one action into an at least one message.

### Claim 5 (depends on 4)

The method of claim 4 further comprising the steps of:
capturing data provided by a user; and
sending the at least one message to an at least one user.

### Claim 6 (depends on 1)

The method of claim 1 wherein the uniform presentation is a graph presentation.

### Claim 7 (depends on 6)

The method of claim 6 wherein the project map is a project graph.

### Claim 8 (depends on 7)

The method of claim 7 wherein the graph presentation comprises an at least one node or an at least one arc.

### Claim 9 (depends on 8)

The method of claim 8 wherein the at least one node or at least one arc comprises relevant information.

### Claim 10 (depends on 8)

The method of claim 8 wherein the at least one node represents an at least one person, an at least one task or an at least one document.

### Claim 11 (depends on 8)

The method of claim 8 wherein the at least one arc represents relationship or function between two nodes.

### Claim 12 (depends on 8)

The method of claim 8 wherein the at least one block of uniform presentation is an at least one event graph.

### Claim 13 (depends on 12)

The method of claim 12 wherein the step of updating the project graph comprises the steps of:
a. adding the at least one event graph to the project graph;
b. determining whether the at least one event graph has an at least one common node with the project graph, and if so determining an impact of the at least one event graph on the project graph;
c. for each of the at least one pattern, performing the steps of:
determining whether the at least one pattern is found within the event graph; and
if the at least one pattern is found within the project graph, merging the at least one pattern with the graph;
d. if an at least one pattern was found within the project graph, performing the steps of determining an impact of the at least one event graph on the project graph, otherwise end the process; and
if step d. is performed less than a predetermined number of times, repeating steps c. and d.

### Claim 14 (depends on 1)

The method of claim 1 wherein the at least one user event is any of the following: creating a new task; initiating a change request; creating an at least one project; adding an at least one task to an at least one project; assigning an at least one task to an at least one person; updating an at least one document; accepting an at least one task; rejecting an at least one task; reassigning at least one task; creating a subtask; reporting task progress or completion.

### Claim 15 (depends on 1)

The method of claim 1 wherein the at least one pattern is any of the following: change request; installation; hardware procurement; software procurement; module testing; prepare testing environment; system test design preparation; system test plan preparation.

### Claim 16 (depends on 2)

The method of claim 2 wherein the at least one action is any of the following: notification of an at least one completed task; notification of an at least one rejected task; notification of an at least one updated document; assignment of an at least one task to an at least one person; notification of an at least one risky situation.

### Claim 17

An apparatus for controlling or managing a process, the apparatus comprising:
a project graph, the project graph comprising:
map data; and
a map handling component;
a synthesis engine for updating the project graph with an at least one event graph;
a conversion component for converting an at least one event graph to or from an at least one action or an at least one event, the conversion component comprising:
a first component for converting an at least one event to an at least one event graph; and
a second component for converting an at least one event graph to an at least one action.

### Claim 18 (depends on 17)

The apparatus of claim 17 wherein the project graph comprises an at least one node or an at least one arc.

### Claim 19 (depends on 18)

The apparatus of claim 18 wherein the at least one node or the at least one arc comprises relevant information.

### Claim 20 (depends on 18)

The apparatus of claim 18 wherein the at least one node represents an at least one person, an at least one task or an at least one document.

### Claim 21 (depends on 18)

The apparatus of claim 18 wherein the at least one arc represents relationship or function between two nodes.

### Claim 22 (depends on 17)

The apparatus of claim 17 further comprising a component for converting an at least one message to or from an at least one user action or an at least one event, the component comprising:
a first component for converting an at least one message into an at least one event; and
a second component for converting an at least one action into an at least one message.

### Claim 23 (depends on 17)

The apparatus of claim 17 further comprising an at least one e-mail interface component, for interfacing with an at least one e-mail program.

### Claim 24 (depends on 23)

The apparatus of claim 23 wherein an at least one e-mail message associated with the apparatus comprises at least one token recognized by an at least one e-mail program.

### Claim 25 (depends on 24)

The apparatus of claim 24 wherein the at least one e-mail message associated with the apparatus comprises a header and the at least one token comprises an at least one identifier embedded in the header.

### Claim 26 (depends on 24)

The apparatus of claim 24 wherein the at least one e-mail message associated with the apparatus comprises a body and the at least one token comprises an at least one tag embedded in the body.

### Claim 27 (depends on 17)

The apparatus of claim 17 further comprising an interface component for interfacing with an at least one external tool, the interface component comprising any one or more of the following:
an at least one productivity tool interface component for interfacing with an at least one productivity tool;
an at least one handheld device interface component, for interfacing with an at least one handheld device;
an at least one document control interface component, for interfacing with an at least one document control system;
an interface wizard component, for generating an at least one interface to an at least one tool or an at least one device or an at least one program.

### Claim 28 (depends on 17)

The apparatus of claim 17 further comprising an at least one communication component for communicating an at least one component within the apparatus with an at least one second component within the apparatus, or an at least one component within the apparatus with an at least one tool or an at least one device or an at least one program.

### Claim 29 (depends on 17)

The apparatus of claim 17 further comprising an at least one security component for providing or restricting at least one privilege to an at least one user or to an at least one task or to an at least one project associated with the apparatus.

### Claim 30 (depends on 17)

The apparatus of claim 17 further comprising an at least one user interface component for collecting data from or showing data to an at least one user of the apparatus.

### Claim 31 (depends on 17)

The apparatus of claim 17 further comprising an at least one diagnostics component for monitoring the apparatus.

### Claim 32 (depends on 17)

The apparatus of claim 17 further comprising an at least one administration component for administrating the apparatus.

### Claim 33

A computer readable storage medium containing a set of instructions for a general purpose computer, the set of instructions comprising:
a project graph, the project graph comprising:
map data; and
a map handling component;
a synthesis engine for updating the project graph with an at least one event graph;
a conversion component for converting an at least one event graph to or from an at least one action or an at least one event, the conversion component comprising:
a first component for converting an at least one event to an at least one event graph; and
a second component for converting an at least one event graph to an at least one action.