Browse Prior Art Database

Task Management and Tracking Invention

IP.com Disclosure Number: IPCOM000126928D
Original Publication Date: 2005-Aug-12
Included in the Prior Art Database: 2005-Aug-12
Document File: 7 page(s) / 125K

Publishing Venue

IBM

Abstract

Disclosed is a framework that solves the problem of how to manage and track efforts within a complex work process in a manner that is flexible, customizable, and robust.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 50% of the total text.

Page 1 of 7

Task Management and Tracking Invention

The framework is flexible in the sense that it can support (in theory) an unlimited number of work processes (from assembling an electrical component to boarding an EDI trading partner). It is customizable in the sense that Logs, Tasks, Task Definitions, Queue Definitions, Workflows, Workflow Definitions, and Users can be created, updated, and deleted at ease. It is robust in the sense that it supports parallel and serial work efforts, automated (with logic) and manual (without logic) User assignments, automated Task progression, reminder notifications, assignment notifications, and detailed metrics. Details of the framework are described below.

Object Structure:

A Log represents an overall work effort. In simple terms, a Log is a container for Tasks. The following items of information are maintained within a Log.

Information Item: Description:

Log Number Unique Log identifier.

Log Description Description of the overall work effort.

Open Timestamp Date and time the Log was placed in an Open status. Customer Unique customer identifier.

Open User User that placed the Log in an Open status.

A Task represents a single piece of work within an overall work effort. Tasks are created from Task Definitions, so they are instances of Task Definitions. The following items of information are maintained within a Task.

Information Item: Description:

Task Number Task identifier unique within a Log. A Log Number and Task

Number form the Tracking Number (i.e. 123-1 where 123 is the Log Number and 1 is the Task Number).

Hours Open Number of hours the task has been in the Open status.

                  Used for detailed metrics (ex. to monitor the efficiency of a work process, to determine trends, to identify trouble areas) Reminder Text Text to be sent to the User assigned to the Task when the current date and time exceed the value stored in Reminder Timestamp.

Reminder Timestamp Date and time the Reminder Text should be sent to the User assigned to the Task.

Open Timestamp Date and time the Task was placed in the Open status. Open User User that placed the Task in the Open status.

Last Modify Timestamp Date and time the Task was last modified.

Last Modify User User that last modified the Task. Queue Queue the Task resides in.

1

Page 2 of 7

User User assigned to the Task.

Status Status of the Task. Valid values include Open (Task is active), Pending (Task is inactive), N/A (Task has been discarded), Closed (Task has been completed), and Hold (Task is temporary suspended).

Log Owner Indicates if the User assigned to the Task owns the overall work effort.

A Workflow represents a collection of similar Tasks that may require coordination between completion of those Tasks. Workflows are created from Workflow Definitions, so they are instances of Workflow Definitions. A Workflow Definition defines Levels and the Tasks associated to the Levels. A Level represents the sequence in which a given Task within a given Workflow must be comple...