Use of a database in a network-based project schedule management system

• US 8,050,953 B2
• Filed: 06/07/2006
• Issued: 11/01/2011
• Est. Priority Date: 06/07/2006
• Status: Active Grant

• Current Assignee: Ricoh Company Limited
• Original Assignee: Ricoh Company Limited
• Inventors: Motoyama, Tetsuro, Fong, Avery
• Primary Examiner(s): Jeanty; Romain
• Application Number:
  US11/449,133
• Publication Number:
  US 20070288290A1
• Time in Patent Office: 1,973 Days
• Field of Search: 705/7
• US Class Current: 705/7.13
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06311 Scheduling, planning or task assignment for a person or group

Abstract

A system is used for the creation, maintenance, and management of an overall project schedule, of individual project member schedules, and of project task assignments over a network. The system comprises three editors accessed through a web browser to perform the various tasks by members of a project. Information is passed between a web server and web browser and a database is used to maintain all information. The project manager can use a task assignment editor to assign tasks to individual project members. The project manager can use a project schedule editor to initially create the project schedule and to show the overall project schedule. After the project schedule is created, each project member can create their own member schedule using a member schedule editor, containing tasks related to the project schedule. After project members complete a task, the project member updates the member'"'"'s schedule via the member schedule editor.

Claims

1. A computer-implemented method for managing a project schedule using a computer database, the method comprising:

storing in a project team database table of a computer database, for each member assigned to perform a task for a project,

a member identifier used to generate member task identifiers that uniquely identify member tasks at each level of a hierarchically-organized task structure;

in response to a particular member requesting completion of a member schedule editor session in which a new subtask was added to a particular level of the hierarchically-organized task structure,

reading, from the project team database table and based on the member identifier for the particular member, the highest task identifier for the particular member for the particular level of the hierarchically-organized task structure,

generating a task identifier for the new subtask by incrementing the highest task identifier for the particular member for the particular level of the hierarchically-organized task structure, wherein the task identifier for the new subtask is specific to both the particular member and the particular level of the hierarchically-organized task structure, and

in the project team database table of the computer database, associating with the new subtask the task identifier generated for the new subtask.

2. The method of claim 1, wherein the step of generating a task identifier for the new subtask includes incrementing the highest task identifier for the particular member for the particular level based on a modulus (MOD) of the member identifier for the particular member.

3. The method of claim 1, further comprising the steps of:

in response to the particular member requesting completion of the member schedule editor session,

storing the new subtask in a member task database table, and

storing, in the project team database table, respective highest task identifiers for the particular member for corresponding levels of the task hierarchy.

4. The method of claim 1, further comprising the step of:

storing a member task database table corresponding to each level of the task hierarchy, wherein member task database tables at adjacent levels of the task hierarchy are linked for aggregating schedule data associated with hierarchically-organized tasks and subtasks.

5. The method of claim 4, further comprising the step of:

storing in a member task database table, in association with a task identifier for a particular subtask, a task identifier for a parent task or parent subtask of the particular subtask.

6. The method of claim 1, further comprising:

storing in the project team database table, for each member assigned to perform a task for the project,

a role identifier associated with access privileges for accessing task assignment, project schedule, and member schedule editors used to interact with the database, and

a directory location at which a corresponding member schedule web page is stored, wherein a member web page displays schedule data contained in one or more tables from the database.

7. The method of claim 1, further comprising the steps of:

storing, in a project task database table, version indicators that identify all corresponding stored versions of schedules for corresponding project tasks.

8. The method of claim 7, further comprising the steps of:

receiving, on a first day, a first planned schedule date for a particular task;

receiving, on a second day that is a different day from the first day, a second planned schedule date for the particular task;

in response to receiving the second planned schedule date on the second day that is different from the first day, updating the version indicator for the particular task to identify a new current version of the schedule for the particular task.

9. The method of claim 1, further comprising the steps of:

storing, in a member task database table, version indicators that identify all corresponding stored versions of schedules for corresponding member subtasks.

10. The method of claim 9, further comprising the steps of:

receiving a first planned schedule date for a first member subtask at a particular level of the task structure hierarchy;

receiving a second planned schedule date for a second member subtask that is a subtask of the first member subtask, wherein the second planned schedule date causes a change to the first planned schedule date;

in response to receiving the second planned schedule date that causes the change to the first planned schedule date, updating the version indicator for the first member subtask to identify a new current version of the schedule for the first member subtask.

11. The method of claim 10, further comprising the steps of:

receiving a third planned schedule date for a third member subtask that is a subtask of the second member subtask, wherein the third planned schedule date causes a change to the second planned schedule date which causes a change to the first planned schedule date;

in response to receiving the third planned schedule date, updating the version indicator for the second member subtask to identify a new current version of the schedule for the second member subtask and updating the version indicator for the first member subtask to identify a new current version of the schedule for the first member subtask.

12. The method of claim 10, wherein the second planned schedule date is received on a second day that is a later day from the first day on which the first planned schedule date is received, the method further comprising:

displaying in a member schedule a second set date corresponding to the second day; and

displaying in the member schedule a first set date, with strikethrough, corresponding to the first day.

13. A non-transitory computer-readable medium for managing a project schedule using a computer database, the non-transitory computer-readable medium storing instructions which, when processed by one or more processors, cause:

storing in a project team database table of a computer database, for each member assigned to perform a task for a project,

a member identifier used to generate member task identifiers that uniquely identify member tasks at each level of a hierarchically-organized task structure;

in response to a particular member requesting completion of a member schedule editor session in which a new subtask was added to a particular level of the hierarchically-organized task structure,

reading, from the project team database table and based on the member identifier for the particular member, the highest task identifier for the particular member for the particular level of the hierarchically-organized task structure,

generating a task identifier for the new subtask by incrementing the highest task identifier for the particular member for the particular level of the hierarchically-organized task structure, wherein the task identifier for the new subtask is specific to both the particular member and the particular level of the hierarchically-organized task structure, and

in the project team database table of the computer database, associating with the new subtask the task identifier generated for the new subtask.

14. The non-transitory computer-readable medium of claim 13, wherein generating a task identifier for the new subtask includes incrementing the highest task identifier for the particular member for the particular level based on a modulus (MOD) of the member identifier for the particular member.

15. The non-transitory computer-readable medium of claim 13, further comprising additional instructions which, when processed by the one or more processors, causes:

in response to the particular member requesting completion of the member schedule editor session,

storing the new subtask in a member task database table, and

storing, in the project team database table, respective highest task identifiers for the particular member for corresponding levels of the task hierarchy.

16. The non-transitory computer-readable medium of claim 13, further comprising additional instructions which, when processed by the one or more processors, causes:

storing a member task database table corresponding to each level of the task hierarchy, wherein member task database tables at adjacent levels of the task hierarchy are linked for aggregating schedule data associated with hierarchically-organized tasks and subtasks.

17. The non-transitory computer-readable medium of claim 16, further comprising additional instructions which, when processed by the one or more processors, causes:

storing in a member task database table, in association with a task identifier for a particular subtask, a task identifier for a parent task or parent subtask of the particular subtask.

18. The non-transitory computer-readable medium of claim 13, further comprising additional instructions which, when processed by the one or more processors, causes:

storing in the project team database table, for each member assigned to perform a task for the project,

a role identifier associated with access privileges for accessing task assignment, project schedule, and member schedule editors used to interact with the database, and

a directory location at which a corresponding member schedule web page is stored, wherein a member web page displays schedule data contained in one or more tables from the database.

19. The non-transitory computer-readable medium of claim 13, further comprising additional instructions which, when processed by the one or more processors, causes:

storing, in a project task database table, version indicators that identify all corresponding stored versions of schedules for corresponding project tasks.

20. The non-transitory computer-readable medium of claim 19, further comprising additional instructions which, when processed by the one or more processors, causes:

receiving, on a first day, a first planned schedule date for a particular task;

receiving, on a second day that is a different day from the first day, a second planned schedule date for the particular task;

in response to receiving the second planned schedule date on the second day that is different from the first day, updating the version indicator for the particular task to identify a new current version of the schedule for the particular task.

21. The non-transitory computer-readable medium of claim 13, further comprising additional instructions which, when processed by the one or more processors, causes:

storing, in a member task database table, version indicators that identify all corresponding stored versions of schedules for corresponding member subtasks.

22. The non-transitory computer-readable medium of claim 21, further comprising additional instructions which, when processed by the one or more processors, causes:

receiving a first planned schedule date for a first member subtask at a particular level of the task structure hierarchy;

receiving a second planned schedule date for a second member subtask that is a subtask of the first member subtask, wherein the second planned schedule date causes a change to the first planned schedule date;

in response to receiving the second planned schedule date that causes the change to the first planned schedule date, updating the version indicator for the first member subtask to identify a new current version of the schedule for the first member subtask.

23. The non-transitory computer-readable medium of claim 22, further comprising additional instructions which, when processed by the one or more processors, causes:

receiving a third planned schedule date for a third member subtask that is a subtask of the second member subtask, wherein the third planned schedule date causes a change to the second planned schedule date which causes a change to the first planned schedule date;

in response to receiving the third planned schedule date, updating the version indicator for the second member subtask to identify a new current version of the schedule for the second member subtask and updating the version indicator for the first member subtask to identify a new current version of the schedule for the first member subtask.

24. The non-transitory computer-readable medium of claim 22, wherein:

the second planned schedule date is received on a second day that is a later day from the first day on which the first planned schedule date is received, and

the non-transitory computer-readable medium further comprises additional instructions which, when processed by the one or more processors, causes;

displaying in a member schedule a second set date corresponding to the second day; and

displaying in the member schedule a first set date, with strikethrough, corresponding to the first day.