Methods and systems for managing hierarchically organized and interdependent tasks and issues
First Claim
1. A computer implemented method of managing a project that includes a plurality of interdependent tasks organized in a hierarchy, comprising the steps of:
- defining the plurality of tasks and storing the defined plurality of tasks in a database stored in a server that is selectively and remotely accessible over a computer network, each of the plurality of tasks having a status associated therewith;
defining a first dependency relationship between each of the defined plurality of tasks to define the hierarchy of tasks and storing the defined first dependencies in the database;
enabling remote retrieval of the status from the database over the computer network and remote updating of the status of any of the plurality of tasks over the computer network;
enabling remote definition of an Issue, a Change Request and a Change Order, the Issue identifying a problem within an identified one of the defined plurality of tasks whose resolution is to be tracked and whose resolution is necessary for the identified task to be completed, the Change Request identifying at least one step to be taken pending authorization to resolve the Issue and the Change Order identifying authorized steps to resolve the Issue, wherein the identified at least one step to be taken to resolve the Issue is included in the Change Order when the Change Request is authorized;
storing the defined Issue, Change Request and Change Order in the database;
requiring remote definition and storage in the database of at least one second dependency relationship between the defined Issue, Change Request and Change Order and the identified task in such a manner that the defined Issue, Change Request and Change Order is integrated into the hierarchy of tasks without changing the defined first dependencies;
associating a document with at least one of the Issue, the Change Request and the Change Order, the document including proposed or authorized steps to resolve the Issue, and storing the associated document in the database, andproviding a selectively and remotely accessible graphical representation of the hierarchy, including the plurality of tasks or selected ones of the plurality of tasks;
the first dependency relationship;
the defined Issue, Change Request or the Change Order, the associated document and the at least one second dependency relationship.
3 Assignments
0 Petitions
Accused Products
Abstract
A method of managing a project including a hierarchy of tasks may include defining and storing tasks. Each of the tasks may include an associated status. A first dependency relationship may be defined between the tasks. Remote retrieval and updating of the status may be enabled. An Issue, a Change Request and/or a Change Order may be remotely defined. The Issue identifies a problem within an identified task whose resolution is to be tracked and is necessary for completion of the identified task, the Change Request identifies step(s) to be taken pending authorization to resolve the Issue and the Change Order identifies authorized step(s) to do so. Remote definition of second dependency relationship(s) may be enabled between the defined Issue, Change Request or Change Order and the identified task to integrate the defined Issue, Change Request or Change Order into the hierarchy without changing the defined first dependencies.
160 Citations
61 Claims
-
1. A computer implemented method of managing a project that includes a plurality of interdependent tasks organized in a hierarchy, comprising the steps of:
-
defining the plurality of tasks and storing the defined plurality of tasks in a database stored in a server that is selectively and remotely accessible over a computer network, each of the plurality of tasks having a status associated therewith; defining a first dependency relationship between each of the defined plurality of tasks to define the hierarchy of tasks and storing the defined first dependencies in the database; enabling remote retrieval of the status from the database over the computer network and remote updating of the status of any of the plurality of tasks over the computer network; enabling remote definition of an Issue, a Change Request and a Change Order, the Issue identifying a problem within an identified one of the defined plurality of tasks whose resolution is to be tracked and whose resolution is necessary for the identified task to be completed, the Change Request identifying at least one step to be taken pending authorization to resolve the Issue and the Change Order identifying authorized steps to resolve the Issue, wherein the identified at least one step to be taken to resolve the Issue is included in the Change Order when the Change Request is authorized; storing the defined Issue, Change Request and Change Order in the database; requiring remote definition and storage in the database of at least one second dependency relationship between the defined Issue, Change Request and Change Order and the identified task in such a manner that the defined Issue, Change Request and Change Order is integrated into the hierarchy of tasks without changing the defined first dependencies; associating a document with at least one of the Issue, the Change Request and the Change Order, the document including proposed or authorized steps to resolve the Issue, and storing the associated document in the database, and providing a selectively and remotely accessible graphical representation of the hierarchy, including the plurality of tasks or selected ones of the plurality of tasks;
the first dependency relationship;
the defined Issue, Change Request or the Change Order, the associated document and the at least one second dependency relationship. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15)
-
-
16. A computer-implemented method of participating in a project that includes a plurality of interdependent tasks organized in a hierarchy, comprising the steps of:
-
accessing a remote database over a computer network, the database storing; a definition of the plurality of tasks, a status associated with each of the defined tasks, and a first dependency relationship between each of the defined plurality of tasks; updating of the status of at least one of the plurality of tasks over the computer network; defining and causing to be stored in the database an Issue, a Change Request and a Change Order, the Issue identifying a problem within an identified one of the plurality of tasks whose resolution is to be tracked and whose resolution is necessary for the identified task to be completed, the Change Request identifying at least one step to be taken pending authorization to resolve Issue and the Change Order identifying authorized steps to resolve the Issue, wherein the identified at least one step to be taken to resolve the Issue is included in the Change Order when the Change Request is authorized; associating a document with at least one of the Issue, the Change Request and the Change Order, the document including proposed or authorized steps to resolve the Issue, and storing the associated document in the database, and defining and storing in the database at least one second dependency relationship between the defined Issue, Change Request and Change Order and the identified task in such a manner that the defined Issue, Change Request and Change Order is integrated into the hierarchy of tasks without changing the defined first dependencies. - View Dependent Claims (17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31)
-
-
32. A computer system configured for managing a project timeline that includes a plurality of interdependent tasks organized in a hierarchy, comprising:
-
at least one processor; at least one data storage device; a plurality of processes spawned by said at least one processor, the processes including processing logic for; defining the plurality of tasks and storing the defined plurality of tasks in a database stored in a server that is selectively and remotely accessible over a computer network, each of the plurality of tasks having a status associated therewith; defining a first dependency relationship between each of the defined plurality of tasks to define the hierarchy of tasks and storing the defined first dependencies in the database; enabling remote retrieval of the status from the database over the computer network and remote updating of the status of any of the plurality of tasks over the computer network; enabling remote definition of an Issue, a Change Request and a Change Order, the Issue identifying a problem within an identified one of the defined plurality of tasks whose resolution is to be tracked and whose resolution is necessary for the identified task to be completed, the Change Request identifying at least one step to be taken pending authorization to resolve the Issue and the Change Order identifying authorized steps to resolve the Issue, wherein the identified at least one step to be taken to resolve the Issue is included in the Change Order when the Change Request is authorized; storing the defined Issue, Change Request and Change Order in the database; requiring remote definition and storage in the database of at least one second dependency relationship between the defined Issue, Change Request and Change Order and the identified task in such a manner that the defined Issue, Change Request and Change Order is integrated into the hierarchy of tasks without changing the defined first dependencies; associating a document with at least one of the Issue, the Change Request and the Change Order, the document including proposed or authorized steps to resolve the Issue, and storing the associated document in the database, and providing a selectively and remotely accessible graphical representation of the hierarchy, including the plurality of tasks or selected ones of the plurality of tasks;
the first dependency relationship;
the defined Issue, Change Request or the Change Order, the associated document and the at least one second dependency relationship. - View Dependent Claims (33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46)
-
-
47. A machine-readable medium having data stored thereon representing sequences of instructions which, when executed by computing device, causes said computing device to manage a project timeline that includes a plurality of interdependent tasks organized in a hierarchy by performing the steps of:
-
defining the plurality of tasks and storing the defined plurality of tasks in a database stored in a server that is selectively and remotely accessible over a computer network, each of the plurality of tasks having a status associated therewith; defining a first dependency relationship between each of the defined plurality of tasks to define the hierarchy of tasks and storing the defined first dependencies in the database; enabling remote retrieval of the status from the database over the computer network and remote updating of the status of any of the plurality of tasks over the computer network; enabling remote definition of an Issue, a Change Request and a Change Order, the Issue identifying a problem within an identified one of the defined plurality of tasks whose resolution is to be tracked and whose resolution is necessary for the identified task to be completed, the Change Request identifying at least one step to be taken pending authorization to resolve the Issue and the Change Order identifying authorized steps to resolve the Issue, wherein the identified at least one step to be taken to resolve the Issue is included in the Change Order when the Change Request is authorized; storing the defined Issue, Change Request and Change Order in the database; requiring remote definition and storage in the database of at least one second dependency relationship between the defined Issue, Change Request and Change Order and the identified task in such a manner that the defined Issue, Change Request and Change Order is integrated into the hierarchy of tasks without changing the defined first dependencies; associating a document with at least one of the Issue, the Change Request and the Change Order, the document including proposed or authorized steps to resolve the Issue, and storing the associated document in the database, and providing a selectively and remotely accessible graphical representation of the hierarchy, including the plurality of tasks or selected ones of the plurality of tasks;
the first dependency relationship;
the defined Issue, Change Request or the Change Order, the associated document and the at least one second dependency relationship. - View Dependent Claims (48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61)
-
Specification