Browse Prior Art Database

Autonomic Project Control System

IP.com Disclosure Number: IPCOM000033448D
Original Publication Date: 2004-Dec-10
Included in the Prior Art Database: 2004-Dec-10

Publishing Venue

IBM

Abstract

Creating autonomy in Project Control (PC) can allow the Project Planning (PP) to manage projects in a better way. Project Management (PM) resources would have less pressure from day to day PC activities. A simple example is leave request processing for employees, which can be performed with initial PP input only.

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 11% of the total text.

Page 1 of 19

Autonomic Project Control System

Autonomic Project Control System

[PC system can demand considerable project management (PM) input, particularly for repetitive projects. Such projects as 'service request', 'change request' '(human) resource request', 'communication request', 'maintenance request' etc. are common with software process outsourcing (SPO), which are those where whole or part of a software department is procured. However, they start with borrowed customers' processes or no process. PM input thins out in project control; whereas the area which is most neglected and requires most attention is project planning (PP), owing to lack of matured processes. APC can thus help PP and control project execution (PE) for better results. In the following some of the well-known PM concepts were used that has relationships with the definition given by the Project Management Body of Knowledge (PMBOK) 2000 without having the same looks. Redefinitions were done to keep the discussion simple and succinct. A project can be of any size.]

APC would have the following characteristics.
1. Process (P ), being bijective mapping between two sets, input (I ) and output (O ): O
I
P

 : . Functional mapping can be one-to-many. In case of process, we would define the input and output with such granularity as would allow one-to-one mapping. An input is a set of resources necessary for another set of resources as output. Thus input constitutes a family, each member of which constitutes an input.

Same thing holds true for output. For example, 2

2

                                ⎯→ ⎯ is a process. Here, the input set may be varied through {water, heat}, {water, electricity}, {water, sound} etc. to find the right input to get {hydrogen, oxygen} as output. The project would map {hydrogen, oxygen} to {water, electricity}.

2. Project (), being the inverse of a process: I O

=P

- :

22 2 O

H

O

H +

1

                         π . This connotes, a project is realized when the process is completely known. The definition of project does not imply that it will give a reverse process. Continuing with our example in endnote i, the project only finds the correct input from among input family to obtain desired output.

3. Resource (r ), being a member of input and/or output: O I r

∈ .

4. Team (T ): T r
T

      : , being a set of resources. Thus input and output are teams: O
T

I

 ℘ ⊂ )

( .

5. A process-team ()

             > ,
T , being a poset ordered by entropy Entropy was introduced with relation to system in Management by Koontz, et al. The dynamic homeostasis of a system requires infusion of negative entropy. In PM literature more importance is given to the process that goes with a system. (>):

         O y
I x y x

   ∈ > ,

   , in the physical sense, which is irreversible The project is only an algebraic inverse of process.. Hence, a project can be realized only by changing input, or learning, being trial and error or conditioning sub-processes. In other words there is no direct way to realize a project by mapping from outpu...