CPM AND PERT Techniques
CPM AND PERT Techniques
RESEARCH PROJECT
Submitted to,
S.S.V. P.G. COLLEGE, HAPUR
Affiliated with
CHAUDHARY CHARAN SINGH UNIVERSITY,
MEERUT
For the degree
MASTERS OF MATHEMATICS
SESSION-2025
Student’s Signature
Barkha Singhal
240028328012
Certificate
This is to certify that the research project entitled “in CPM and PERT
Technology” submitted by Barkha Singhal, a student of M.Sc.
Mathematics, Department of Mathematics, S.S.V. P.G. College, Hapur
(affiliated to Chaudhary Charan Singh University, Meerut), has been
carried out under my supervision and guidance.
To the best of my knowledge, the work presented in this project is original
and authentic. It has not been submitted, either wholly or in part, for the
award of any other degree or diploma in this or any other university or
institution.
I consider this project suitable for submission in partial fulfillment of the
requirements for the degree of Master of Science in Mathematics for the
academic session 2025.
Date: 27th May, 2025
Place: Hapur
First and foremost, I am truly grateful to my academic supervisor, Dr. Sharad Kumar,
for their invaluable guidance, constant encouragement, and insightful feedback at every
stage of this research. Their deep expertise in CPM and PERT Technology provided
the essential foundation for this work, and their constructive suggestions allowed me to
refine my approach and improve the quality of the research. I feel incredibly fortunate to
have had the opportunity to learn from such a knowledgeable and supportive mentor.
This project would not have been possible without the contributions, sacrifices, and
support of all these remarkable individuals.
Abstract
This project explores the application of Critical Path Method
(CPM) and Program Evaluation and Review Technique
(PERT) as essential tools in project management. Both
techniques are widely used for planning, scheduling, and
controlling complex projects. CPM focuses on identifying the
longest sequence of dependent activities (the critical path) to
ensure timely project completion, while PERT incorporates
probabilistic time estimates to manage uncertainty and
variability in project durations. This project demonstrates the
practical implementation of CPM and PERT through case
studies and simulation models, highlighting their effectiveness
in optimizing project timelines, resource allocation, and risk
assessment. The findings emphasize how integrating these
methodologies enhances decision-making processes and
contributes to more efficient and successful project execution
across various industries.
Introduction to CPM / PERT Techniques
PERT (Project Evaluation and Review Technique) was devised in 1958 for
the POLARIS missile program by the Program Evaluation Branch of the
Special Projects office of the U.S.Navy, helped by the Lockheed Missile
Systems division and the Consultant firm of Booz-Allen & Hamilton. The
calculations were so arranged so that they could be carried out on the IBM
Naval Ordinance Research Computer (NORC) at Dahlgren, Virginia
Mathematically simple
Limitations of PERT/CPM
1. Planning
2. Scheduling
The ultimate objective of the scheduling phase is to prepare a
time chart showing the start and finish times for each activity
as well as its relationship to other activities of the project.
Moreover the schedule must pinpoint the critical path
activities which require special attention if the project is to be
completed in time.
For non-critical activities, the schedule must show the
amount of slack or float times which can be used
advantageously when such activities are delayed or when
limited resources are to be utilized effectively.
3. Allocation of resources
Essentially, there are six steps which are common to both the
techniques. The procedure is listed below:
I. Define the Project and all of its significant activities or tasks. The
Project (made of several tasks) should have only a single start activity
and a single finish activity.
II. Develop the relationships among the activities. Decide
which activities must precede and which must follow
others.
III. Draw the "Network" connecting all the activities. Each
Activity should have unique event numbers. Dummy
arrows are used where required to avoid giving the same
numbering to two activities.
VI. Use the Network to help plan, schedule, and monitor and control the
project.
1. Activity
Any individual operation which utilizes resources and has an end
and a beginning is called activity. An arrow is commonly used to
represent an activity with its head indicating the direction of
progress in the project. These are classified into four categories
1. Predecessor activity – Activities that must be completed
immediately prior to the start of another activity are called
predecessor activities.
2. Event
An event represents a point in time signifying the completion of
some activities and the beginning of new ones. This is usually
represented by a circle in a network which is also called a node or
connector.
The events are classified in to three categories
1. Merge event – When more than one activity comes and joins
an event such an event is known as merge event.
3. Sequencing
The first prerequisite in the development of network is to maintain
the precedence relationships. In order to make a network, the
following points should be taken into considerations
What job or jobs precede it?
What job or jobs could run concurrently?
What job or jobs follow it?
What controls the start and finish of a job?
Since all further calculations are based on the network, it is necessary
that a network be drawn with full care.
Rule 1
Each activity is represented by one and only one arrow in the network
Rule 2
No two activities can be identified by the same end events
Rule 3
In order to ensure the correct precedence relationship in the arrow
diagram, following questions must be checked whenever any
activity is added to the network
What activity must be completed immediately before this
activity can start?
What activities must follow this activity?
What activities must occur simultaneously with this activity?
1. Dangling
3. Redundancy
Step 2
i. Earliest starting time of activity (i, j) is the earliest
event time of the tail end event i.e. (Es)ij = Ei
ii. Earliest finish time of activity (i, j) is the earliest
starting time + the activity time i.e. (Ef)ij = (Es)ij + Dij or
(Ef)ij = Ei + Dij
Step 1
For ending event assume E = L. Remember that all E’s
have been computed by forward pass computations.
Step 2
Latest finish time for activity (i, j) is equal to the latest
event time of event j i.e. (Lf)ij = Lj
Step 3
Latest starting time of activity (i, j) = the latest
completion time of (i, j) – the activity time or (Ls) ij
=(Lf)ij - Dij or (Ls)ij = Lj - Dij
Step 4
Latest event time for event ‘i’ is the minimum of the
latest start time of all activities originating from that
event i.e. Li = min [(Ls)ij for all immediate successor of
(i, j)] = min [(Lf)ij - Dij] = min [Lj - Dij]
Example 1
Determine the early start and late start in respect of all node
points and identify critical path for the following network.
Solution
Calculation of E and L for each node is shown in the network
From the table, the critical nodes are (1, 2), (2, 5), (5, 7), (5, 8), (7,
10) and (8, 10)
Example 2
Find the critical path and calculate the slack time for the following
network
Solution
The earliest time and the latest time are obtained below
From the above table, the critical nodes are the activities (1, 3), (3, 5)
and (5, 9)
Example 1
For the project
Task: A B C D E F G H I J K
Least time: 4 5 8 2 4 6 8 5 3 5 6
Greatest 8 10 12 7 10 15 16 9 7 11 13
time:
Most likely 5 7 11 3 7 9 12 6 5 8 9
time:
Find the earliest and latest expected time to each event and
also critical path in the network.
Solution
Greatest time Most likely Expected time
Task Least time(t0)
(tp) time (tm) (to + tp + 4tm)/6
A 4 8 5 5.33
B 5 10 7 7.17
C 8 12 11 10.67
D
2 7 3 3.5
E 4 10 7 7
F 6 15 9 9.5
G 8 16 12 12
H 5 9 6 6.33
I 3 7 5 5
J 5 11 8 8
K 6 13 9 9.17
References
[1] J. J. Moder, C. R. Phillips, and E. W. Davis, Project Management
with CPM, PERT and Precedence Diagramming, 3rd ed. New York:
Van Nostrand Reinhold, 1983.