AU2000240338A1 - Method and apparatus for a closed loop real time working assignment tracking system - Google Patents

Description

METHOD AND APPARATUS FOR A CLOSED LOOP REAL TIME WORKING ASSIGNMENT TRACKING SYSTEM

FIELD OF INVENTION

The field of the present invention relates generally to a personal computer

(PC) and client-server based, multi-tiered, closed-loop accountability tracking systems

for various activities and work assignments being conducted in an organization, and

more specifically relates to systems for real time assignment and status tracking and

reporting of projects and their associated tasks and actions, the assignment of these

activities to individuals or functions, and the tracking of the status of these activities

whether open, past due, or completed.

BACKGROUND OF INVENTION

It has long been recognized that for an organization to be successful it must

have the ability to plan, schedule, and track its various activities from initiation to

completion. Many different systems have been developed over the years, with

improvements being conceived at a much more rapid pace since the advent of

programmable computers. However, even with the improvements that have been

made through the use of personal computers, large scale computers, laptop computers,

and so forth, all programmed via software for tracking various activities, available

tracking systems, particularly in large enterprises are lacking in many aspects. For example, many organizations find that over the vears multiple different processes

have been instituted in the organization in order to track various activities on an

ongoing basis This results in a fragmented tracking and reporting system that tends

to make management lack any real time visibility as to the ongoing activities in the

system Because of the fragmentation, it is extremely difficult to collate information

Even if information can be collated, it is very time consuming to do so and to provide

reports that are meaningful to management Even with present computerized systems,

work assignments and status tracking tend to both labor and paper intensive

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the present invention are described below with

reference to the drawings, in which like items are identified by the same reference

designation, wherein

Figure 1 is a simplified block schematic diagram of the present svstem

showing various hardware,

Figure 2 shows a block schematic diagram for the cascading of various tiers of

activities.

Figure 3 shows a flowchart of the overall steps provided in the system and

programming of the personal computer (PC) of Figure 1 for one embodiment of the

invention. Figures 4 through 7 show detailed flowcharts that are cascaded together in a

sequential manner for carrying out the process or method of Figure 3 for various

embodiments of the invention:

Figures 8 through 19 show examples of various screens and menus applicable

for use in association with various steps called out in the flowcharts of Figures 3

through 7;

Figure 20 shows an example of a "Pareto Chart" of top findings sources for

displaying information generated in the system of the present invention; and

DESCRIPTION OF THE INVENTION AND PREFERRED EMBODIMENTS

The present invention provides a method for a computerized client-server

based, multi-tiered, closed loop accountability tracking system for various work

assignments, the system including a central database selectively receiving data from

either one or a combination of a plurality of personal computers, internet input

screens, and/or electronic mail messaging, and being programmed for providing

between participants real-time response and reporting capabilities, and real-time

notification of system events, with each user of the system having a personal

computer or work station coupled to a network with other users. The inventive

method steps include: initiating on-line an unlimited number of first tiered activities

under the control of an associated initiator for recordation in said system: assigning

and recording on-line an unlimited number of second and lower tier activities to

individuals or organizations, making such individuals or organizations responsible for

completing said activities: and maintaining current activity status for each of said first tier activities and their associated second and lower tier activities in real time via

either one or a combination of on-line updating capabilities, and/or automatically

generated electronic mail messages, and/or the internet.

With reference to Figure 1 , in an engineering prototype of the present

invention, each user of the present system requires at least a personal computer 2,

keyboard 4. monitor 6. and a link to a centralized database 8. The centralized

database may reside on the user^'s computer 2 or on a remote host computer (not

shown). In addition, in a preferred embodiment, each user may also be provided a

printer 10. an electronic digital scanner 12 for documents and photographs, a digital

camera 14 or other digital imaging apparatus, and appropriate computer memory 15.

In an alternate configuration, a user can interface with the system using similar

equipment described above except that an internet connection 16 is used instead of or

in addition to direct linking to the central database.

The system is programmed as shown in the overall process flowchart of Figure

3. For the purposes of this description, first tier activities are referred to as "Projects."

second tier activities are referred to as "Tasks," and third tier activities are referred to

as "Actions". In the engineering prototype, the system was designed for

implementing requirements of the International Standards Organization (ISO) and

provides for the establishment of an unlimited number of Projects (see Figure 2), each

assigned an individual unique identifier. As further shown in Figure 2. a user can

then, in a cascading manner, assign an unlimited number of second tier Tasks for each

Project. In a like manner, a user can also assign an unlimited number of third tier

Actions for each second tier Task. Each Project. Task, and Action is tracked

independently but linked together by a common identification system so that a user can instantly see the current status of all tiers of activities associated with their

project. The engineering prototype cascades two tiers of assignments but the system

can be expanded to include an unlimited number of tiers.

As will be discussed in greater detail below, the prototype system.

known by the inventor under the title "Systems and Process Improvement Network"

(SPIN), proved the capability of the present system to provide up to the minute (real

time), notification of work assignments through use of existing electronic mail

message systems, real time response submittal, review, acceptance and reporting

capabilities, and the real time visibility of historical problems and trends through use

of built in and user defined graphs, charts, and reports. The system is programmed to

automatically integrate data applicable to specific Projects, Tasks and Actions. The

Projects. Tasks, and Actions are tracked in a closed-loop manner until each tier has

been completed. Therefore, no second tier activity can be closed out until all of its

associated third tier activities have been closed. Further a first tier activity cannot be

closed until all of its associated second tier activities are closed.

With further reference to Figure 3, the top level method or process steps of the

present invention will now be described in detail. At the initial installation of the

system and anytime thereafter, a system administrator sets or updates (step 300)

system defaults and preferences and populates or edits a number of database fields

that can be later selected by general system users through drop-down menus, on¬

screen icons, or similar mechanisms. This information can include but is not limited

to authorized user names, user access levels, and edit rights, passwords, electronic

mail addresses and similar user information: customer and supplier information such as addresses, telephone and facsimile telephone numbers, and contact names:

Preformatted text, and similar basic information established for the specific system

configuration and intended use. Once these initial system controls are established, a

person responsible for managing a Project, hereafter referred to as a Project Owner or

"PO" can create or initiate a Project on-line, as shown by step 310 by operating PC 2

to open a Project Screen and adding a new record by use of an on-screen icon, drop¬

down menu selection, or similar mechanism (see Figure 9). The new Project is

assigned its own unique identifier. This unique identifier is automatically assigned by

the system and then used by the system to link any second, third tier, or lower tier

activities. The identifier can be any numeric or alphanumeric string but typically

consists of the year followed by a sequential number. Next, in step 320. the Project

Owner proceeds to initiate one or more Tasks by use of an on-screen icon, drop-down

menu selections, or similar mechanism (see Figure 1 1 ). Note that for purposes of this

description, the terminology "Project" and '"Activity" are used interchangeably to

denote a first tier activity while "Task". "Issue^" and "Finding^" are used

interchangeably to denote a second tier activity, and "Action" is used to denote a third

tier activity. With reference to the Project. Issues, Response and Action screens of

Figures 8. 10, 14, and 16, all of the data necessary for documenting the activity is

entered directly into applicable fields, selected from drop down menus previously

populated by the system administrator, or automatically entered by the system based

upon built-in coded instructions or programming. Data may be text or graphic images

obtained from a digital scanner 12. a digital camera 14. or similar digital image source

as well as objects or text generated by software programs outside the scope of this

invention. Data can also be obtained via electronic mail. Further, the Project Owner assigns the activity to a specific person or function (hereafter referred to as the Task

Owner or "TO") to develop a Plan and complete the task. Note that the function can

be an organization such as a subcontracting company, for example. As the Project

Owner enters data, the present system searches the established database for similar

issues, based upon criteria controlled by the user or preset by the system

administrator, and displays a prompt screen (see Figures 12 and 1 8) if the issue just

entered appears to be a recurrence or duplicate assignment, and allows the user to

view applicable historical information based upon the search. After completion of the

fields, the Project Owner notifies the Task Owner of the work assignment by use of an

on-screen icon, drop-down menu selection, or similar mechanism. The system then

automatically composes an electronic mail message, customized to the Task Owner,

and containing information pertinent to the work assignment. The system

accomplishes this by selecting applicable key information from the database and

formatting it into a concise message. The system is programmed to then date stamp

the notification, set response due dates, lock certain fields from further editing, and

thereafter send the electronic mail message to the assigned Task Owner. In addition,

at the same time a similar electronic mail message is automatically sent to other key

personnel as established by the system administrator.

Next, in step 330, the assigned Task Owner must develop a plan for

completing the assignment and then respond by documenting the plan on-line or. in a

preferred embodiment, via an intranet connection. After documenting the Plans, the

Task Owner then notifies the Project Owner via submittal of an automatically

generated electronic mail message that the plan is available for review . This

notification is accomplished by use of an on-screen icon, drop-down menu selection. or similar mechanism The system automatically generates the submittal message

based upon information selected from the central database, locks the text of the

response, and sets the response date

Note that although a particular configuration of screens are shown in the

examples of Figures 8 - 20, each can be reconfigured in any desired manner for

providing the various requirements of the present system, and as such these examples

are not meant to be limiting Numerous other pop-up screens, data fields, and menus

can be utilized for various applications, and any icons shown on the screens can be

replaced by drop-down menu selections and similar mechanisms Figures 9 and 1 1

show examples of pop-up screens that can be used to input additional information

associated with a Project

As shown in step 340, the Project Owner reviews the Plan provided by the

Task Owner, and can take action to either accept or reject the plan through similar

electronic mail as already described above In Figure 15 a pop-up screen is shown as

used in the prototype system, for example, for permitting the Project Owner to easily

carry out step 340 The Project Owner advises the Task Owner of acceptance or

reiection of the Response by activating the appropriate icon, whereby the system

automatically electronically sends the answer to the Task Owner Also, if the Project

Owner elects, the Response bv the Task Owner to the Task can be sent to higher

management for permitting them to respond to the Plan This is accomplished bv

addressing the appropriate icon The next step 350 to "Initiate Actions" is entered by the Task Owner for

assigning detailed Actions through on-line communications to an appropriate Action

Owner or Action Owners. The screen example shown in Figure 16 was used in a

prototype system, for permitting a Task Owner to prepare an unlimited number of

detailed actions for each Response. After the Actions are entered, the system is

programmed to track each Action until the Action is completed. In this regard.

Project Owners can track closure of Tasks, or identify systemic problems for insuring

root cause corrective action is taken, through use of the pull-down screen of Figure

19. for example. In this regard, to "Close Task" in step 380, the Project Owner upon

learning a Task is complete, addresses a pull-down menu provided for closing the

Task. However, a Project Owner cannot close a Task in step 380. until step 370 has

been carried out for "Review And Close Actions". Pull-down screens are used for

permitting the Task Owners to first review the status of Actions via on-line

communication, for closing out such Actions when completed as shown by reports

from Action Owner or Owner(s). After the Task Owner has reported via step 370 to

the Project Owner that the Actions are completed, the Project Owner then initiates

step 380 to "Close Task" when completed. Lastly, in step 390. after a Project Owner

has learned from on-line communication that all Tasks associated with a given Project

have been closed, the Project itself is then closed through the use of the appropriate

Project Screen. For example, see Figure 8.

Details of the steps that must be programmed into the PC 2 for each one of the

high tier flowchart steps of Figure 3 are shown in the flowcharts of Figures 4 through

7. With reference to Figures 3 and 4. step 310 is carried out via the detailed steps 400. 402. 404. and 406. respectively. The following step 320 for initiating Tasks is carried

out by the detailed steps 410, 412. 414, 416. 418. 420. 422, and 424, followed to

completion via steps 500. 502, 504, 506. 508. and 510, as shown in Figure 5.

With reference to Figures 3 and 5. step 330 for responding to a Task is carried

out in this example via steps 512, 514, 516, 518. 520, and 522. The following step

340 for the Project Owner's review of a Task Owner's Plan is carried out as shown in

Figure 6 via steps 602, 604, 606, 608, 610. 612. 614. 616. and 618.

The next step is for a Task Owner to Initiate Actions as shown in Figure 6 via

steps 620, 622, 624, 626, 628, and 630, proceeding to steps shown in Figure 7

including steps 700, 706, 712, 714, and 716.

With further reference to Figures 3 and 7, the next step 370 for both reviewing

and closing actions by Task Owners of the step is carried out by the detailed steps

718, 720, 722, 724. and 726, as shown.

With further reference to Figures 3 and 7. the next step 380 for Close Tasks is

carried out by the detailed steps 702. 704, 708. and 710. The last step 390 for closing

a project is then completed via steps 728 and 730.

The detailed steps of Figures 4 through 7 for carrying out the broad steps of

Figure 3 are as incorporated in the prototype system. These steps are not meant to be

limiting, in that the arrangement of these steps, and the inclusion of additional steps may be required depending upon a particular Application. For any particular

Application, the steps must be programmed into the computer system of Figure 1.

The present system, as proven by a prototype thereof, can support digital

images or photographs for historical reference. The digital images can be inputted

into the system through the use of the equipment such as a digital scanner 12 or digital

camera 14 shown in Figure 1.

As further proven in the prototype system of the present invention, the system

meets various International Standards Organization (ISO) requirements via priority

editing. For example, the prototype system was proven to meet ISO9000

requirements for preventive action for small to medium size businesses or facilities.

Through the use of pull-down menus and summary screens, the system is user friendly

requiring no extensive computer skills, technical computer staff, or other extensive

training of users. For example, in the prototype system, the system is programmed to

open to a Summary Screen of Tasks. The user, such as a Task Owner, can then decide

to see a listing of all Tasks or only Tasks assigned to the particular Task Owner.

From the Summary Screen, one can then proceed directly to review details for a

particular Task by addressing a row on the screen relating to the Task of Interest.

Similarly, the system provides Summary Screens for Projects, and for Responses.

The Summary Screens are in the form of menus permitting one to proceed to review

details of Projects. Responses, or Reports through appropriate cursor addressing of

portions or a particular screen. With further reference to the screens of Figures 8 and 10. Figure 8. as

previously described, shows a Project Screen providing project details for a particular

Project. Similarly, Figure 10 shows an Issue Screen providing Issue details.

The system is programmed to permit customer information to be provided, if

necessary. In Figure 9 a screen is shown for presenting Customer Information, as

programmed into the prototype system. The prototype system as programmed

provides for the display of a cursor addressable Custom Information icon or button for

pulling-up the screen of Figure 8.

The prototype system has also been programmed to permit a user working on a

particular project to write personal notes that only are available or visible to that

particular user. The notes can be programmed into the system, such as notes for

projects, and notes for responses. The system is programmed to retain such notes

until a user owner thereof deletes them.

The prototype system is programmed to respond to the addressing of a

"Notify" button or icon for automatically generating a customized electronic mail

message, for detailing the ISO requirement or any other requirement that can be

specified. Further, the system is programmed for transmitting a similar electronic

mail message to that of Figure 13 associated with Responses that are ready for review

whenever a Response has been accepted or rejected, or when an Issue must be

escalated to a higher level of management for response. The system is programmed to

fill in the name of the Process Owner or Action Owner automatically, and thereafter transmitting a copy of an electronic mail message to an ISO Element Leader, if

required.

As shown in Figure 12, the system also is programmed for including a built-in

history feature that automatically looks for similar prior problems analogous to a

particular Task that has been just created or inputted into the system. The system is

further programmed for permitting such a history check to be made at any time by

addressing a cursor to a "History" button or icon provided on certain pull-down

screens or menus, such as shown in Figure 10. As shown in Figure 19. a pull-down

menu screen is provided for obtaining certain "charts and graphs" that can be

automatically generated in the system. Figure 20 shows an example of a "Pareto Chart

Of Findings Sources" programmed into the prototype system. Similarly, as shown in

Figure 17. specific Reports can be called up through use of the screen example shown.

Also, the prototype system is programmed to provide a custom report window for

allowing a user to display a variety of information for analyzing particular problems

in trends. With reference to the example of the screen of Figure 18. a user selects a

particular "Filter Criteria" for selecting how the user desires certain data to be

displayed in a report. The system then is programmed to create the desired report

automatically.

In summary, the present method and apparatus provides a computerized multi-

tiered, real-time, on-line, closed-loop system for permitting users to track various

activities, for enhancing the efficiency of their particular organization. The system

provides for the management of facts and actual data for various projects, while avoiding the problems of establishing necessary tasks to be resolved through guess

work which is counter productive. The system permits users to obtain patterns for

predicting problems or tasks that must be resolved multiple times. The system is

programmed to automatically screen prior records for identifying Tasks that are

similar to particular Tasks just inputted into the system, and provides a screen for

reviewing any such prior tasks records uncovered. The system can be implemented

through use of an internal network, and through use of a secured internet system. The

system is also programmed to provide a system administrator with the ability to

monitor all activities, set priorities, set time lines, and implement other controls over

the system.

Although various embodiments of the present invention have been shown and

described herein, they are not meant to be limiting. Those of skill in the art may

recognize certain modifications to these embodiments, which modified embodiments

are meant to be covered by the spirit and scope of the appended claims. For example.

the present invention can be applied for use in a doctor's or dentist's office for

scheduling patients, tracking progress with their treatment, and completion of their

treatment. Also, the invention can also be applied for use in manufacturing facilities,

for customer service tracking, and any other work efforts requiring multi-tiers, the

tracking of activities and tasks, and accountability for completion.

Claims (33)

What Is Claimed Is:

1. A method for a computerized client-server based, multi-tiered, closed

loop accountability tracking system for various work assignments, said system

including a central database selectively receiving data from either one or a

combination of a plurality of personal computers, internet input screens, and/or

electronic mail messaging, and being programmed for providing between participants

real-time response and reporting capabilities, and real-time notification of system

events, each user of said system having a personal computer or work station coupled

to a network with other users, said method comprising the steps of:

initiating on-line an unlimited number of first tiered activities under the

control of an associated initiator for recordation in said system;

assigning and recording on-line an unlimited number of second and

lower tier activities to individuals or organizations, making such individuals or

organizations responsible for completing said activities: and

maintaining current activity status for each of said first tier activities

and their associated second and lower tier activities in real time via either one or a

combination of on-line updating capabilities, and/or automatically generated

electronic mail messages, and/or the internet.

2. The method of claim 1. further including the step of:

automatically setting and tracking various due dates for

activities.

3. The method of claim 1. further including the step of:

automatically generating electronic mail message reminders of

said due dates.

4. The method of claim 1. further including the step of:

automatically locking and unlocking access to activity information

responsive to either one or both of system and communication events, including

assignment notifications, response submittals. activity completions, and similar status

updates, and user access levels and edit rights.

5. The method of claim 1. further including the step of:

maintaining user access levels and edit rights to initiate, respond to. or

edit activity information.

6. The method of claim 1. further including the step of:

automatically generating various status and history charts, graphs, and

reports based upon user input.

7. The method of claim 1. further including the step of:

providing complete on-line visibility of all activities and their status to

authorized system users.

8. The method of claim 1. further including the step of:

limiting authority rights to initiate and/or edit system controls and

defaults to designated system administrators.

9. The method of claim 1 , further including the step of:

independently maintaining authority rights and prohibitions for

each activity tier, and each activity within each tier.

10. The method of claim 1 , further including the step of:

automatically updating said database responsive to all

successive user inputs.

1 1. A method for a computerized client-server based, multi-tiered, closed

loop accountability tracking system for various work assignments, said system

including a central database selectively receiving data from either one or a

combination of a plurality of personal computers, internet input screens, and/or

electronic mail messaging, and being programmed for providing between participants

real-time response and reporting capabilities, and real-time notification of system

events, each user of said system having a personal computer or work station coupled

to a network with other users, said method comprising the steps of: initiating on-line an unlimited number of first tiered activities under the

control of an associated initiator for recordation in said system;

assigning and recording on-line an unlimited number of second and

lower tier activities to individuals or organizations, making such individuals or

organizations responsible for completing said activities:

maintaining current activity status for each of said first tier activities

and their associated second and lower tier activities in real time via either one or a

combination of on-line updating capabilities, and/or automatically generated

electronic mail messages, and/or the internet;

automatically setting and tracking various due dates for activities:

automatically generating electronic mail message reminders of said

due dates;

automatically locking and unlocking access to activity information

responsive to either one or both of system and communication events, including

assignment notifications, response submittals. activity completions, and similar status

updates, and user access levels and edit rights;

maintaining user access levels and edit rights to initiate, respond to. or

edit activity information;

automatically generating various status and history charts, graphs, and

reports based upon user input;

providing complete on-line visibility of all activities and their status to

authorized system users; and

limiting authority rights to initiate and/or edit system controls and

defaults to designated system administrators.

12. The method of claim 1 1. wherein said user maintaining step further

includes the step of:

independently maintaining authority rights and prohibitions for each activity tier, and each activity within each tier.

13. The method of claim 1 1 , further including the step of:

automatically updating said database responsive to all

successive user inputs.

14. A method for a computerized closed loop assignment and tracking

system for multiple projects, associated tasks and subtasks. and associated actions for

resolving respective tasks, said system being programmed for providing between

participants real-time response and reporting capabilities, and real-time notification of

system events, each user of said system having a personal computer or work station

coupled to a network with other users, said method comprising the steps of:

initializing of said system by a System Administrator;

initiating on-line a new project under control of a Project Owner for

recordation in said system;

assigning and recording on-line one or more Tasks to Task Owner(s).

said Project Owner making said assignments, said Task Owner(s) being responsible

for completing said Task(s); notifying via electronic mail message said Task Owners of said Tasks

assigned to them, respectively: documenting and recording on-line by said Task Owner(s) of Plans to

complete assigned Task(s);

notifying via electronic mail message from said Task Ovvner(s) to said

Project Owner that Plans for completing Task(s) are ready for on-line review;

notifying via electronic mail message from said Project Owner to said

Task Owner(s) of acceptance or rejection of said Plans; unlocking the Plan, if rejected,

for revision and resubmittal;

assigning and recording on-line detailed Actions for accepted plans to

individuals designated as Action Owners, said Task Owner(s) making the assignments

of said Actions for completing respective Task(s);

notifying via electronic mail said Action Owners of said Actions

assigned to them, respectively;

closing out and recording on-line by a said Task Owner of the

completion of Actions relative to a given Task;

closing out and recording on-line by a said Project Owner of completed

Task(s): and

closing out and recording on-line by a Project Owner of a Project in

which all Tasks are closed.

15. The method of Claim 14, wherein said new project initiation step

further includes the steps of:

assigning an independent and unique project identifier: and

recording in a computer memory all project details for access-on-line.

16. The method of Claim 14, wherein said step of assigning tasks further includes the steps of:

determining if a Task is a first Task for the associated Project;

creating a Task identifier linked to the associated project identifier, if a

first Task is determined;

assigning a next sequential Task identifier for the associated Project, if

the Task is not a first Task;

saving in a memory the Task identifier;

receiving Task details from the associated Project Owner; and

saving in memory the Task details.

17. The method of Claim 16, further including the steps of:

searching for similar prior Tasks; and

creating a report for presenting details of any similar prior Tasks

uncovered.

18. The method of Claim 16, further including the steps of:

establishing an initiation date and completion date for an associated

Plan;

creating a customized electronic mail message based upon Task

requirements and other data residing in a centralized database:

locking said Task; and

saving in memory all dates.

19. The method of Claim 14, wherein the step of a Task Owner notifying a

Project Owner of a Plan for completing a Task further includes the steps of:

recording the date of such notification:

creating a customized electronic mail message based upon Plan inputs:

locking said Plan from editing except by System Administrators; and

saving in memory the notification date.

20. The method of Claim 19, wherein said step of notifying a Task Owner

of the acceptance or rejection of a Plan, further includes for a rejection the steps of:

recording and saving the date of rejection;

creating a customized electronic mail message based upon Task inputs

and

unlocking said Plan for revision by the Task Owner.

21. The method of Claim 20. further including the step of:

notifying via electronic mail message from said Task Owner(s) to said

Project Owner that revised Plans for completing Task(s) are ready for on-line review,

its response to a prior rejection.

22. The method of Claim 21. further including the step of :

locking the revised Plan from editing except by a System

Administrator.

23. The method of Claim 14, wherein said step of notifying a Task Owner of the acceptance of a Plan further includes the steps of:

creating an electronic mail message based upon Task inputs:

setting an acceptance date for said Task: and

saving in memory the acceptance date, and associated Task inputs.

24. The method of Claim 14, wherein said step of assigning Actions

further includes the steps of:

determining whether a new Action is a first Action for an associated

Task; creating an Action identifier linked to the associated Task identifier, if

a first Action is determined;

assigning a next sequential Action identifier for the Task/Project if the

Action is not a first Action; and

automatically saving all Action inputs in memory.

25. The method of Claim 24, further including the steps of:

documenting on-line by the Task Owner and Action Owner the status

of each Action; and

automatically saving in memory the status of each Action.

26. The method of Claim 14, wherein said Actions close out step further

includes the step of: automatically saving in memory all inputs associated with the closing

of Actions

27 The method of Claim 14 wherein said step of assigning Actions further includes the steps of

setting all Action completion dates, and

automatically saving in memory the Action completion dates

28 The method of Claim 14, further including the steps of

closing a Project upon receipt of notice of closure of all Tasks and

Actions, and

automatically saving in memory all closure information or data

29 The method of Claim 14, wherein said Task Owners notifying step b

Pro)ect Owners further includes the step of

locking details of the Task assignments from editing except bv System

Administrators

30 The method of Claim 14, wherein said Project Owner notifying step bv

Task Owners of Plans further includes the step of

locking the Plans from editing except bv System Administrators

31 The method of Claim 14, wherein said step of notifying Action Owners

ot Actions assigned to then further includes the step of locking the Action assignments from editing except by a Systems

Administrator.

32. The method of Claim 14. further including the steps of:

tracking independently each Project. Task, and Action: and

linking together each Project, and its associated Tasks, and associated

Actions, via a common identification system, for permitting a user to as required

review the current status of all levels of activities associated with a given Project.

33. A method for a computerized closed loop assignment and tracking

system for multiple projects, associated tasks and subtasks, and associated actions for

resolving respective tasks, said system being programmed for providing between

participants real-time response and reporting capabilities, and real-time notification of

system events, each user of said system having a personal computer or work station

coupled to a network with other users, said method comprising the steps of:

initializing said system by a System Administrator;

initiating on-line a new project under control of a Project Owner for

recordation in said system;

assigning and recording on-line one or more Tasks to Task Owner(s).

said Project Owner making said assignments, said Task Owner(s) being responsible

for completing said Task(s);

notifying via electronic mail message said Task Owners of said Tasks

assigned to them, respectively; locking details of the Task assignments from editing except by System

Administrator;

documenting and recording on-line by said Task Owner(s) of Plans to

complete assigned Task(s):

notifying via electronic mail message from said Task Owner(s) to said

Project Owner that Plans for completing Task(s) are ready for on-line review;

locking the Plans from editing except by System Administrator:

notifying via electronic mail message from said Project Owner to said

Task Owner(s) of acceptance or rejection of said Plans;

reacting to rejection of a plan by taking the steps including:

recording and saving the date of rejection;

creating a customized electronic mail message based upon Task inputs

and unlocking said Plan for revision by a Task Owner;

notifying via electronic mail message from said Task Owner(s) to said

Project Owner that revised Plans for completing Task(s) are ready for on-line review.

in response to a prior rejection;

locking the revised Plan from editing except by a System

Administrator.