# US 2006/0053125 A1 · System and method for network-based project management

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

- Number: US 2006/0053125 A1
- Document ID: US20060053125A1
- Status: Published application
- Kind: A1
- Application number: 11/247,132
- Filed: 2005-10-12
- Published: 2006-03-09
- Earliest claimed: 2002-10-02
- Assignees: Bank One Corporation
- Inventors: Kelly Scott
- Web page: https://patentgrep.com/patent/US20060053125A1

## CPC

- G06Q 10/04: Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem" (market predictions or forecasting for commercial activities G06Q30/0202)
- G06Q 10/10: Office automation; Time management
- Y10S 707/99943: Generating database or data structure, e.g. via user interface
- Y10S 707/99945: Object-oriented database structure processing
- Y10S 707/99948: Application of database or data structure, e.g. distributed, multimedia, or image
- 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
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

A system for managing a project and its associated information over a network is presented. The system includes a project information database associated with the network and a project information management tool. The project information database stores information associated with a project being carried out by a corporate entity having at least one sub-entity. The project information management tool includes a project information module to manage the information associated with the project, and at least one cross-sub-entity project-component module. The cross-sub-entity project module manages and tracks overall information and sub-entity specific information, of the information associated with the project, related to the project-component.

## Claims

### Claim at position 1

-37. (canceled)

### Claim 38

A project management system, comprising:
a project database associated with a network, the project database storing information associated with at least one project being carried out by at least a first entity having at least one sub-entity;
a project management tool including:
a project information module to manage information associated with the at least one project, and
at least one project-component module to manage at least sub-entity specific project information, in cooperation with the project information module; and
at least one user system connected to the network to access the project management tool over the network, based on an access level associated with the user.

### Claim 39 (depends on 38)

The system of claim 38, wherein the at least one sub-entity comprises at least one of a line of business of a corporation, a division of a corporation, a subsidiary of a corporation and a support unit of the corporation.

### Claim 40 (depends on 38)

The system of claim 38, wherein the project database comprises a relational database.

### Claim 41 (depends on 38)

The system of claim 38, wherein the project management tool is configured to interface with at least one other project management system, so that a one time entry allows a user to access the at least one other project management system.

### Claim 42 (depends on 38)

The system of claim 38, wherein the project management tool further comprises a search module to search the project database for information requested by other modules within the project management tool to create at least one of displays and reports.

### Claim 43 (depends on 38)

The system of claim 38, wherein the at least one project-component module comprises at least one or more of a home module, a project information module, a milestones module, an issues module, a change controls module, a documents module, a project status reports module, a team member status reports module, a contacts module, a management decisions module, a meetings module, an action items module, a financials module, a new items module, a search module, an archive module, a project management system coordinator module and a central project management system administrator module.

### Claim 44 (depends on 38)

The system of claim 38, wherein the at least one project-component module allows each sub-entity of the first entity to produce at least one report, wherein the at least one report comprises at least one of a consolidated report and a individualized sub-entity report.

### Claim 45 (depends on 38)

The system of claim 38, wherein the project database stores information associated with a plurality of projects.

### Claim 46 (depends on 38)

The system of claim 38, wherein the project-component module allows a user to create a customized representation of the project-component module related information in the project database.

### Claim 47

A method for managing a project comprising:
a) storing project information for a first project, with associations to at least one project component so that all of the project information related to each project component is accessible by a user on a network when the at least one project component is retrieved, the project information including project information related to at least one sub-unit of an entity performing the project;
b) generating at least one project component record based on the associations to the at least one project component for managing the project; and
c) generating a project component display, customized to a project component and based on the at least one project component record, when the at least one project component is accessed by a user, the project component display having links to project component related documents and project component related reports and available to at least one user system over the network.

### Claim 48 (depends on 47)

The method of claim 47, wherein user access is restricted, based on an access level associated with the user.

### Claim 49 (depends on 47)

The method of claim 47, wherein the at least one project component record comprises a financial record.

### Claim 50

A system for managing a project comprising:
means for storing project information, for a first project, with associations to at least one project component so that all of the project information related to each project component is accessible by a user on a network when the project component is retrieved, the project information including project information related to at least one sub-unit of an entity performing the project;
means for generating at least one project component record based on the associations to the at least one project component for managing the project; and
means for generating a project component display, customized to a project component and based on the at least one project component record, when the project component is accessed by a user, the project component display having links to project component related documents and project component related reports and available to at least one user system over the network.

### Claim 51 (depends on 50)

The system of claim 50, wherein user access is restricted, based on an access level associated with the user.

### Claim 52 (depends on 50)

The system of claim 50, wherein the at least one project component record comprises a financial record.

### Claim 53

A method for managing a project comprising the steps of:
storing project information for a first project, with associations to at least one project component so that all of the project information related to each project component is accessible by a user on a network when the at least one project component is retrieved, the project information including project information related to at least one sub-unit of an entity performing the project;
generating at least one project component record based on the associations to the at least one project component for managing the project;
generating a project component display, customized to a project component and based on the at least one project component record, when the at least one project component is accessed by a user, the project component display having links to project component related documents and project component related reports and available to at least one user system over the network;
checking a status identifier of a user for identifying the user's status, wherein the step of generating the at least one project component record comprises a step of generating a project component record based on the user's status and the step of generating the project component display comprises a step of generating the project component display based on the user's status;
identifying one or more functions associated with the user, based on the user's status wherein the user's status comprises one or more of reader status, editor status, coordinator status and administrator status; and
presenting the user with one or more project management sub-units based on the user's status.

### Claim 54 (depends on 53)

The method of claim 53, wherein the one or more functions comprise access capabilities.

### Claim 55

A system for managing a project comprising:
means for storing project information for a first project, with associations to at least one project component so that all of the project information related to each project component is accessible by a user on a network when the at least one project component is retrieved, the project information including project information related to at least one sub-unit of an entity performing the project;
means for generating at least one project component record based on the associations to the at least one project component for managing the project;
means for generating a project component display, customized to a project component and based on the at least one project component record, when the at least one project component is accessed by a user, the project component display having links to project component related documents and project component related reports and available to at least one user system over the network;
means for checking a status identifier of a user for identifying the user's status, wherein the step of generating the at least one project component record comprises a step of generating a project component record based on the user's status and the step of generating the project component display comprises a step of generating the project component display based on the user's status;
means for identifying one or more functions associated with the user, based on the user's status wherein the user's status comprises one or more of reader status, editor status, coordinator status and administrator status; and
means for presenting the user with one or more project management sub-units based on the user's status.

### Claim 56 (depends on 55)

The system of claim 55, wherein the one or more functions comprise access capabilities.
