




Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
What is project management? What its need? How to work in team, alone on a project? What are its parts? How to divide work? How to plan? What is project scope? This course has answer for how to make organization successful. This handout includes: Network, Introduction, Project, Manaegement, Budgers, Planning, Reasonable, Interrelationship, Dependencies
Typology: Lecture notes
1 / 8
This page cannot be seen from the preview
Don't miss anything!





Introduction Benefits and Advantages of Scheduling Historical Evolution of Network Scheduling Network Fundamentals and Terminology Pert/CPM and their Difference Graphical Evaluation and Review Techniques (GERT) Dependencies or Interrelationship Slack Time
28.1 Introduction:
In today’s highly competitive environment, management is continually seeking new and better control techniques to cope with the complexities, masses of data, and tight deadlines that are characteristic of many industries. In addition, management is seeking better methods for presenting technical and cost data to customers.
Since World War II, scheduling techniques have taken on paramount importance. The most common of these techniques are shown below:
28.2 Benefits and Advantages of Scheduling:
The Program Evaluation and Review Technique (PERT) perhaps is the best known of all the relatively new techniques. PERT has several distinguishing characteristics:
a) How time delays in certain elements influence program completion? b) Where slack exists between elements? c) What elements are crucial to meet the completion date?
The above-mentioned benefits apply to all network scheduling techniques, not just PERT.
28.3 Historical Evolution of Networks:
Before going further with the details, let us have an insight into the historical evolution of networks. PERT was originally developed in 1958 and 1959 to meet the needs of the "age of massive engineering" where the techniques of Taylor and Gantt were inapplicable. The Special Projects Office of the U.S. Navy, concerned with performance trends on large military development programs, introduced PERT on its Polaris Weapon System in 1958, after the technique had been developed with the aid of the management consulting firm of Booz, Allen, and Hamilton. Since that time, PERT has spread rapidly throughout almost all industries. At about the same time the Navy was developing PERT, the DuPont Company initiated a similar technique known as the Critical Path Method (CPM) , which also has spread widely, and is particularly concentrated in the construction and process industries.
The basic requirements of PERT/time as established by the Navy, in the early 1960s, were as follows:
28.3.1 Advantages of PERT:
must be identified so that a master plan can be developed that provides an up-to-date picture of operations at all times and is easily understood by all.
The interdependencies are shown through the construction of networks. Network analysis can provide valuable information for planning, integration of plans, time studies, scheduling, and resource management. The primary purpose of network planning is to eliminate the need for crisis management by providing a pictorial representation of the total program.
The following management information can be obtained from such a representation:
As we know that networks are composed of events and activities. An event is defined as the starting or ending point for a group of activities, and an activity is the work required to proceed from one event or point in time to another. Figure 28.1 below shows the standard nomenclature for PERT networks. The circles represent events, and arrows represent activities. The numbers in the circles signify the specific events or accomplishments. The number over the arrow specifies the time needed (hours, days, months), to go from event 6 to event 3. The events need not be numbered in any specific order. However, event 6 must take place before event 3 can be completed (or begin).
Figure 28.1: Standard PERT Nomenclature
As depicted in Figure 28.2 (a) above, event 26 must take place prior to events 7, 18, and 31. In Figure 28.2 (b), the opposite holds true, and events 7, 18, and 31 must take place prior to event
However, these charts can be used to develop the PERT network, as shown in Figure 28. below. The bar chart in Figure (A) below can be converted to the milestone chart in Figure (B) below. By then defining the relationship between the events on different bars in the milestone chart, we can construct the PERT chart in Figure (C) below.
Figure 28.3: Conversion from Bar Chart to PERT Chart
Basically PERT is a management planning and control tool. It can be considered as a road map for a particular program or project in which all of the major elements (events) have been completely identified together with their corresponding interrelations. PERT charts are often constructed from back to front because, for many projects, the end date is fixed and the contractor has front-end flexibility.
It is important to note here that one of the purposes of constructing the PERT chart is to determine how much time is needed to complete the project. PERT, therefore, uses time as a common denominator to analyze those elements that directly influence the success of the project, namely, time, cost, and performance. The construction of the network requires two inputs. First, a selection must be made as to whether the events represent the start or the completion of an activity. Event completions are generally preferred.
Therefore, by using PERT we can now identify the earliest possible dates on which we can expect an event to occur, or an activity to start or end. There is nothing overly mysterious about this type of calculation, but without a network analysis the information might be hard to obtain.
PERT charts can be managed from either the events or the activities. For levels 1–3 of the Work Breakdown Structure (WBS), the project manager's prime concerns are the milestones, and therefore, the events are of prime importance. For levels 4–6 of the Work Breakdown Structure (WBS), the project manager's concerns are the activities.
28.5 Differences Between PERT and CPM:
Note that the principles that we have discussed so far apply not only to PERT, but to CPM as well. The nomenclature is the same for both, and both techniques are often referred to as arrow diagramming methods, or activity-on-arrow networks. The differences between PERT and CPM are as follows:
28.6 Graphical Evaluation And Review Technique (GERT):
Graphical Evaluation and Review Techniques (GERT) are similar to PERT but have the distinct advantages of allowing for looping, branching, and multiple project end results. With PERT one cannot easily show that if a test fails, we may have to repeat the test several more times. With PERT, we cannot show that, based upon the results of a test, we can select one of several different branches to continue the project. These problems are easily overcome using GERT.
28.7 Dependencies or Interrelationships:
There are three basic types of interrelationships or dependencies:
1. Mandatory Dependencies (i.e., Hard Logic): These are dependencies that cannot change, such as erecting the walls of a house before putting up the roof. 2. Discretionary Dependencies (i.e., Soft Logic): These are dependencies that may be at the discretion of the project manager or may simply change from project to project. As an example, one does not need to complete the entire bill of materials prior to beginning procurement.
3. External Dependencies: These are dependencies that may be beyond the control of the project manager such as having contractors sit on your critical path.
28.7.1 Dummy Activities:
It is sometimes impossible to draw network dependencies without including dummy activities. Dummy activities are artificial activities, represented by a dotted line, and do not consume resources or require time. They are added into the network simply to complete the logic.
In the Figure 28.5 below, the dummy activity is required to show that D is preceded by A and B.
Figure 28.5: Dummy Activity
28.8 Slack Time:
It is essential to know that since there exists only one path through the network that is the longest, the other paths must be either equal in length to or shorter than that path. Therefore, there must exist events and activities that can be completed before the time when they are actually needed. The time differential between the scheduled completion date and the required date to meet critical path is referred to as the slack time. In Figure 28.4, event 4 is not on the crucial path. To go from event 2 to event 5 on the critical path requires seven weeks taking the route 2–3–5. If route 2–4–5 is taken, only four weeks are required. Therefore, event 4, which requires two weeks for completion, should begin anywhere from zero to three weeks after event 2 is complete. During these three weeks, management might find another use for the resources of people, money, equipment, and facilities required to complete event 4.
Therefore, the critical path is vital for resource scheduling and allocation because the project manager, with coordination from the functional manager, can reschedule those events not on the critical path for accomplishment during other time periods when maximum utilization of resources can be achieved, provided that the critical path time is not extended. This type of rescheduling through the use of slack times provides for a better balance of resources throughout the company, and may possibly reduce project costs by eliminating idle or waiting time.