Consolidation of member schedules with a project schedule in a network-based management system

• US 8,799,043 B2
• Filed: 06/07/2006
• Issued: 08/05/2014
• 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): Padot, Timothy
• Application Number:
  US11/449,130
• Publication Number:
  US 20070288289A1
• Time in Patent Office: 2,981 Days
• Field of Search: 705/7.13, 705/7.17, 705/301
• 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
• CPC Class Codes: G06Q 10/1097 Task assignment

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 using a database to manage a project schedule for a project, the computer-implemented method comprising:

storing, by one or more computing devices, in a project task database table, via a project schedule editor session, planned schedule dates for a plurality of project tasks for the project;

storing, by one or more computing devices, in a first-level member task database table from a set of hierarchically-related member task database tables, via a member schedule editor session conducted by a particular project member,

planned schedule dates for a subtask of a particular project task from the plurality of project tasks, wherein the subtask is defined by the particular project member during the member schedule editor session and is assigned to the particular project member, and

planned schedule dates for an existing non-project task assigned to the particular project member, wherein the existing non-project task is defined by the particular project member during the member schedule editor session, and;

wherein the project task database table is linked to the planned schedule dates for the existing non-project task assigned to the particular project member contained in the first-level member task database table and wherein each member task database table other than the lowest level member task database table in the set of hierarchically-related member task database tables is linked to planned schedule dates contained in a respective next-lower-level member task database table;

retrieving, by one or more computing devices, from the first-level member task database table and displaying in a member schedule web page, both the planned schedule dates for the subtask of the particular project task from the plurality of project tasks and the schedule dates for the existing non-project task assigned to the particular project member; and

displaying in a project schedule web page a project schedule for the project that includes the plurality of project tasks without displaying the existing non-project task assigned to the particular project member.

2. The computer-implemented method of claim 1, further comprising:

receiving, via the member schedule editor session for the particular project member, a request to update schedule dates for subtasks assigned to the particular project member; and

in response to the request to update the schedule dates for subtasks assigned to the particular project member, for each subtask displaying a planned start date for as the earliest planned start date of all lower level subtasks of the subtask and displaying a planned end date as the latest planned end date of all the lower level subtasks of the subtask.

3. The computer-implemented method of claim 2, further comprising:

receiving, via the member schedule editor session for the particular project member, a request to finish the member schedule editor session for the particular project member; and

in response to the request to finish the member schedule editor session for the particular project member, storing the displayed planned start dates and the planned end dates for each level of subtask in a corresponding member task table.

4. The computer-implemented method of claim 3, wherein receiving and displaying are performed by one or more client computing devices, and wherein the steps of storing are performed by one or more server computing device.

5. The computer-implemented method of claim 1, further comprising:

receiving, via the project schedule editor session, a request to consolidate schedule dates for subtasks of the plurality of project tasks for the project;

in response to the request to consolidate schedule date for subtasks of the plurality of project tasks for the project,

retrieving, from the first-level member task database table, schedule dates for subtasks of the plurality of project tasks for the project;

aggregating the retrieved schedule dates, by for each project task from the plurality of project tasks for the project,

setting a planned start date as the earliest planned start date, from the hierarchically-related member task database tables, for all levels of subtasks of the project task, and

setting a planned end date as the latest planned end date, from the hierarchically-related member task database tables, for all levels of the subtasks of the project task;

storing, in the project task database table, the planned start dates and the planned end dates for each project task from the plurality of project tasks for the project; and

displaying the project schedule for the project in the project schedule web page by displaying the planned start dates and the planned end dates for each project task from the plurality of project tasks for the project.

6. The computer-implemented method of claim 5, wherein the aggregating is performed by one or more server computing devices.

7. The computer-implemented method of claim 1, further comprising displaying a member schedule for the particular project member in a member schedule web page, wherein the member schedule includes the existing non-project task assigned to the particular project member.

8. The computer-implemented method of claim 7, wherein displaying a member schedule includes displaying the existing non-project task assigned to the particular project member with a visual indication that indicates that the existing non-project task is a non-project task.

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

storing in a project task database table, via a project schedule editor session, planned schedule dates for a plurality of project tasks for the project;

storing in a first-level member task database table from a set of hierarchically-related member task database tables, via a member schedule editor session conducted by a particular project member,

planned schedule dates for a subtask of a particular project task from the plurality of project tasks, wherein the subtask is defined by the particular project member during the member schedule editor session and is assigned to the particular project member, and

planned schedule dates for an existing non-project task assigned to the particular project member, wherein the existing non-project task is defined by the particular project member during the member schedule editor session, and;

wherein the project task database table is linked to the planned schedule dates for the existing non-project task assigned to the particular project member contained in the first-level member task database table and wherein each member task database table other than the lowest level member task database table in the set of hierarchically-related member task database tables is linked to planned schedule dates contained in a respective next-lower-level member task database table;

retrieving from the first-level member task database table and displaying in a member schedule web page, both the planned schedule dates for the subtask of the particular project task from the plurality of project tasks and the schedule dates for the existing non-project task assigned to the particular project member; and

displaying in a project schedule web page a project schedule for the project that includes the plurality of project tasks without displaying the existing non-project task assigned to the particular project member.

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

receiving, via the member schedule editor session for the particular project member, a request to update schedule dates for subtasks assigned to the particular project member; and

in response to the request to update the schedule dates for subtasks assigned to the particular project member, for each subtask displaying a planned start date for as the earliest planned start date of all lower level subtasks of the subtask and displaying a planned end date as the latest planned end date of all the lower level subtasks of the subtask.

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

receiving, via the member schedule editor session for the particular project member, a request to finish the member schedule editor session for the particular project member; and

in response to the request to finish the member schedule editor session for the particular project member, storing the displayed planned start dates and the planned end dates for each level of subtask in a corresponding member task table.

12. The non-transitory computer-readable medium of claim 11, wherein receiving and displaying are performed by one or more client computing devices, and wherein the steps of storing are performed by one or more server computing devices.

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

receiving, via the project schedule editor session, a request to consolidate schedule dates for subtasks of the plurality of project tasks for the project;

in response to the request to consolidate schedule date for subtasks of the plurality of project tasks for the project,

retrieving, from the first-level member task database table, schedule dates for subtasks of the plurality of project tasks for the project;

aggregating the retrieved schedule dates, by for each project task from the plurality of project tasks for the project,

setting a planned start date as the earliest planned start date, from the hierarchically-related member task database tables, for all levels of subtasks of the project task, and

setting a planned end date as the latest planned end date, from the hierarchically-related member task database tables, for all levels of the subtasks of the project task;

storing, in the project task database table, the planned start dates and the planned end dates for each project task from the plurality of project tasks for the project; and

displaying the project schedule for the project in the project schedule web page by displaying the planned start dates and the planned end dates for each project task from the plurality of project tasks for the project.

14. The non-transitory computer-readable medium of claim 13, wherein the aggregating is performed by one or more server computing devices.

15. The non-transitory computer-readable medium of claim 9, further comprising additional instructions which, when processed by the one or more processors, cause displaying a member schedule for the particular project member in a member schedule web page, wherein the member schedule includes the existing non-project task assigned to the particular project member.

16. The non-transitory computer-readable medium of claim 15, wherein displaying a member schedule includes displaying the existing non-project task assigned to the particular project member with a visual indication that indicates that the existing non-project task is a non-project task.

17. An apparatus for using a database to manage a project schedule for a project, the apparatus comprising a memory storing instructions which, when processed by one or more processors, cause:

storing in a project task database table, via a project schedule editor session, planned schedule dates for a plurality of project tasks for the project;

storing in a first-level member task database table from a set of hierarchically-related member task database tables, via a member schedule editor session conducted by a particular project member,

planned schedule dates for a subtask of a particular project task from the plurality of project tasks, wherein the subtask is defined by the particular project member during the member schedule editor session and is assigned to the particular project member, and

planned schedule dates for an existing non-project task assigned to the particular project member, wherein the existing non-project task is defined by the particular project member during the member schedule editor session, and;

wherein the project task database table is linked to the planned schedule dates for the existing non-project task assigned to the particular project member contained in the first-level member task database table and wherein each member task database table other than the lowest level member task database table in the set of hierarchically-related member task database tables is linked to planned schedule dates contained in a respective next-lower-level member task database table;

retrieving from the first-level member task database table and displaying in a member schedule web page, both the planned schedule dates for the subtask of the particular project task from the plurality of project tasks and the schedule dates for the existing non-project task assigned to the particular project member; and

displaying in a project schedule web page a project schedule for the project that includes the plurality of project tasks without displaying the existing non-project task assigned to the particular project member.

18. The apparatus of claim 17, wherein the memory stores additional instructions which, when processed by the one or more processors, cause:

receiving, via the member schedule editor session for the particular project member, a request to update schedule dates for subtasks assigned to the particular project member; and

in response to the request to update the schedule dates for subtasks assigned to the particular project member, for each subtask displaying a planned start date for as the earliest planned start date of all lower level subtasks of the subtask and displaying a planned end date as the latest planned end date of all the lower level subtasks of the subtask.

19. The apparatus of claim 18, wherein the memory stores additional instructions which, when processed by the one or more processors, cause:

receiving, via the member schedule editor session for the particular project member, a request to finish the member schedule editor session for the particular project member; and

in response to the request to finish the member schedule editor session for the particular project member, storing the displayed planned start dates and the planned end dates for each level of subtask in a corresponding member task table.

20. The apparatus of claim 17, wherein the memory stores additional instructions which, when processed by the one or more processors, cause:

receiving, via the project schedule editor session, a request to consolidate schedule dates for subtasks of the plurality of project tasks for the project;

in response to the request to consolidate schedule date for subtasks of the plurality of project tasks for the project,

retrieving, from the first-level member task database table, schedule dates for subtasks of the plurality of project tasks for the project;

aggregating the retrieved schedule dates, by for each project task from the plurality of project tasks for the project,

setting a planned start date as the earliest planned start date, from the hierarchically-related member task database tables, for all levels of subtasks of the project task, and

setting a planned end date as the latest planned end date, from the hierarchically-related member task database tables, for all levels of the subtasks of the project task;

storing, in the project task database table, the planned start dates and the planned end dates for each project task from the plurality of project tasks for the project; and

displaying the project schedule for the project in the project schedule web page by displaying the planned start dates and the planned end dates for each project task from the plurality of project tasks for the project.