Methods and apparatus for managing information on activities of an enterprise

• US 5,655,118 A
• Filed: 03/21/1994
• Issued: 08/05/1997
• Est. Priority Date: 03/21/1994
• Status: Expired due to Term

• Current Assignee: TTI Inventions C LLC (Intellectual Ventures LLC)
• Original Assignee: Bell Communications Research, Inc. (Telefonaktiebolaget LM Ericsson)
• Inventors: Schlieber, Karl Johannes, Heindel, Lee Edward, Kasten, Vincent Alan
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US08/215,756
• Time in Patent Office: 1,233 Days
• Field of Search: 395/600, 364/419.19, 364/461, 382/13
• US Class Current: 705/7.17
• CPC Class Codes: G06Q 10/063118 Staff planning in a project environment
• CPC Class Codes: G06Q 10/06313 Resource planning in a project environment
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99936 Pattern matching access
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A system for maintaining various information representative of activities of an enterprise having four components. The first component creates the information including project data, subproject data, task data, and employee data. The second component stores the project data, the subproject data, the task data, and the employee data. The third component creates non-hierarchical relationship keys among the project data, the subproject data, the task data, and the employee data stored by the storing means; and the fourth component updates the project data, the subproject data, the task data, and the employee data stored by the storing means and for updating the relationship keys among the project elements, the subproject elements, the task elements, and the employee elements.

Claims

1. A system for storing and maintaining information representative of activities of an enterprise, said system comprising:

means for creating the information including project data, subproject data, task data, and employee data, wherein each of the data includes elements;

means for storing the project data, the subproject data, the task data, and the employee data;

means for creating nonhierarchical relationship keys among the project data, the subproject data, the task data, and the employee data stored by the storing means, wherein the relationship keys relate elements of the project data to each other or to elements of the subproject, task, and employee data, the relationship keys relate elements of the subproject data to each other or to elements of the project, task, and employee data, the relationship keys relate elements of the task data to each other or to elements of the project, subproject, and employee data, and the relationship keys relate elements of the employee data to each other or to elements of the project, subproject, and task data; and

means for updating the project data, the subproject data, the task data, and the employee data stored by the storing means and for updating the relationship keys among the project data elements, the subproject data elements, the task data elements, and the employee data elements.

2. The system of claim 1 further comprising means for accessing the project data, the subproject data, the task data, and the employee data stored by the storing means.

3. A system for storing and maintaining activity information corresponding to activities of an enterprise, said system comprising:

means for creating the activity information including planning data, product data, project data, subproject data, task data, and employee data, wherein each of the data includes elements;

means for storing the planning data, the product data, the project data, the subproject data, the task data, and the employee data;

means for creating nonhierarchical relationship keys among the planning data, the product data, the project data, the subproject data, the task data, and the employee data stored by the storing means, wherein the relationship keys relate elements of the planning data to each other or to elements of the product, project, subproject, task, and employee data, the relationship keys relate elements of the product data to each other or to elements of the planning, project, subproject, task, and employee data, the relationship keys relate elements of the project data to each other or to elements of the planning, product, subproject, task, and employee data, the relationship keys relate elements of the subproject data to each other or to elements of the planning, product, project, task, and employee data, the relationship keys relate elements of the task data to each other or to elements of the planning, product, project, subproject, and employee data, and the relationship keys relate elements of the employee data to each other or to elements of the planning, product, project, subproject, and task data; and

means for updating the planning data, the product data, the project data, the subproject data, the task data, and the employee data stored by the storing means and for updating the relationship keys among the planning data elements, the product data elements, the project data elements, the subproject data elements, the task data elements, and the employee data elements.

4. The system of claim 3 wherein the updating means includes means for accessing the planning data, the product data, the project data, the subproject data, the task data, and the employee data stored by the storing means.

5. The system of claim 3 wherein the relationship keys between the employee data and the task data are created such that a plurality of elements of employee data relate to a single element of the task data.

6. The system of claim 3 wherein the relationship keys between the task data and the subproject data are created such that a plurality of elements of task data relate to a single element of the subproject data.

7. The system of claim 3 wherein the relationship keys between the subproject data and the project data are created such that a plurality of elements of subproject data relate to a single element of the project data.

8. The system of claim 3 wherein the relationship keys between the project data and the product data are created such that a plurality of elements of project data relate to a single element of the product data.

9. The system of claim 3 wherein the relationship keys between the product data and the planning data are created such that a plurality of elements of product data relate to a single element of the planning data.

10. A system for storing and maintaining various activity information corresponding to activities of an enterprise, said memory system comprising:

means for creating the activity information including project data elements, subproject data elements, task data elements, and employee data elements;

means for storing the project data elements, the subproject data elements, the task data elements, and the employee data elements;

means for creating nonhierarchical relationship connections among the project data elements, the subproject data elements, the task data elements, and the employee data elements stored by the storing means such that two or more of the employee data elements connect to a single element of the task data elements and two or more of the task data elements connect to a single element of the subproject data elements and two or more of the subproject data elements connect to a single element of the project data elements; and

means for updating the project data, the subproject data, the task data, and the employee data stored by the storing means and for updating the relationship connections among the project data elements, the subproject data elements, the task data elements, and the employee data elements.

11. A computer-implemented method for holding and maintaining information representative of activities of an enterprise in a computer having a memory, and a microprocessor, said computer-implemented method comprising the steps of:

creating the information including project data, subproject data, task data, and employee data, wherein each of the data includes elements;

storing the project data, the subproject data, the task data, and the employee data in the memory;

creating nonhierarchical relationship keys among the project data, the subproject data, the task data, and the employee data stored by the memory, wherein the relationship keys relate elements of the project data to each other or to elements of the subproject, task, and employee data, the relationship keys relate elements of the subproject data to each other or to elements of the project, task, and employee data, the relationship keys relate elements of the task data to each other or to elements of the project, subproject, and employee data, and the relationship keys relate elements of the employee data to each other or to elements of the project, subproject, and task data;

updating the project data, the subproject data, the task data, and the employee data stored by the memory; and

updating the relationship keys among the project data elements, the subproject data elements, the task data elements, and the employee data elements.

12. The computer-implemented method of claim 11 further comprising the step of:

accessing the project data, the subproject data, the task data, and the employee data stored by the storing means.

13. A computer-implemented method for holding and maintaining activity information representative of activities of an enterprise in a computer having a memory, and a microprocessor, said computer-implemented method comprising the steps of:

creating the activity information including project data elements, subproject data elements, task data elements, and employee data elements;

storing the project data elements, the subproject data elements, the task data elements, and the employee data elements in the memory;

creating nonhierarchical relationship connections among the project data elements, the subproject data elements, the task data elements, and the employee data elements stored by the memory such that two or more of the employee data elements connect to a single element of task data elements and two or more of the task data elements connect to a single element of the subproject data elements and two or more of the subproject data elements connect to a single element of the project data elements; and

updating the project data, the subproject data, the task data, and the employee data stored by the memory and for updating the relationship connections among the project data elements, the subproject data elements, the task data elements, and the employee data elements.